Brief
Meridian Home Insurance is an invented independent broker that arranges home insurance for households in one county, with specialist cover for listed buildings, flood-risk homes and landlords. It has run a website for years, redesigned it last spring, and has seen enquiries from search fall since. The owner wants a plan for the next quarter, not an audit report to file.
Constraints you must work within:
- A freelance developer is available for a limited number of days, so technical work must be grouped into a few template-level changes.
- The owner and one freelance writer produce content, and every page about cover goes through the firm's compliance review before publishing, which slows production.
- The firm will not buy links or pay for placements.
- The owner needs to see, each month, whether the plan is working in terms of quote requests, not rankings alone.
Apply the SEO strategy framework to the whole brief: health of each pillar, the current constraint, and a sequence that follows dependency.
The site and its data
Meridian Home Insurance: site inventory and Search Console
| Section | Indexable URLs | Template | Notes |
|---|---|---|---|
| Homepage | 1 | Home | Links to a "Services" index, not to product pages |
| Product pages | 7 | Product | Buildings, contents, combined, listed buildings, flood-risk, landlord, holiday homes |
| Town pages | 64 | Location | "Home insurance in [town]", same copy with the name changed |
| FAQ pages | 41 | FAQ | One question per URL; 30 are linked from nowhere |
| Blog posts | 296 | Article | Archive paginated by date; tag pages with sort parameters |
| Search Console indexing state | URLs | Example |
|---|---|---|
| Excluded by noindex tag | 3 | /landlord-insurance, /flood-risk-home-insurance, /holiday-home-insurance |
| Crawled, currently not indexed | 52 | /home-insurance-in-ashcombe |
| Duplicate without user-selected canonical | 140 | /blog/tag/claims?sort=new |
| Blocked by robots.txt | 18 | /quote/step-2 (intended) |
| Page with redirect | 210 | Old domain URLs from the redesign |
Core Web Vitals, mobile field data: product template poor for LCP (hero image lazy-loaded); quote widget on product pages poor for INP. Click depth: product pages sit four clicks from the homepage.
Meridian Home Insurance: rankings, links and outcomes
| Cluster | Current owner(s) | Average position | Note |
|---|---|---|---|
| listed building insurance | /listed-buildings-insurance | 8 | Best performer |
| flood risk home insurance | none (noindexed) | not ranking | Ranked on page one before the redesign |
| landlord insurance [county] | none (noindexed) | not ranking | |
| home insurance [county] | homepage and town pages, swapping | 15 | |
| what does buildings insurance cover | blog post and FAQ page, swapping | 22 |
Links: about 90 referring domains. Strongest: county newspaper features, a heritage trust's resource page linking to the listed buildings page, insurer panel pages. Two of the press links point at old URLs that now pass through two redirects. A dozen generic directory listings; no manufactured pattern.
Analytics, last full quarter against the same quarter last year: non-brand organic sessions down 31%; quote requests from organic landing pages down from 140 to 85; product pages carried 62% of organic quote requests before the redesign.
The figures are invented to make the exercise concrete; your reasoning matters more than the arithmetic.
Task
- Audit and score. Follow the method in the technical SEO audit tutorial, with the technical SEO audit checklist open, and rate every criterion in the technical SEO audit scorecard as missing, partial or solid. Score the gates first, record the band and say which findings drive it. Spot-check the noindexed product pages with the SEO page checker to confirm what the reports show.
- Name the constraint. Using the five pillars, write a short paragraph saying which pillar is holding visibility back now, with the evidence, and which comes next. Say whether Crawl BudgetHow much a search engine crawls a site. is a factor for a site of this size, and why.
- Write the technical backlog. Turn every partial or missing row into a developer-ready ticket: what is wrong, which template, example URLs, what correct looks like and how to verify it in GSCGoogle's search performance and indexing tool.. Order the tickets by pages affected and their value against effort, and group them into as few releases as the developer's time allows.
- Map the content work. Build a keyword map for the clusters in the data, as in the garden centre mapping exercise. Decide what happens to the town pages, the competing blog post and FAQ, and the orphaned FAQs. List the pages to create or improve, and write one of them up with the content brief template, noting the compliance review in the schedule.
- Plan the link work. Review the profile with the link quality and anchor text guide, as you did in the backlink sample exercise. Decide what to reclaim, what to leave and which two sources of new links fit the specialist products, without paid placements.
- Sequence the quarter. Lay out the work week by week or fortnight by fortnight across technical, content, links and measurement, respecting the developer's days and the compliance review. Mark dependencies.
- Define the measurement plan. Choose the KPIA metric tied directly to an objective. chain from coverage to quote requests, with segments, baselines and the annotation log, following the SEO KPIs and reporting guide. Name the Search Console and analytics reports you will read for each, using the Google Analytics reports and dimensions guide to pair landing page with the right session metrics. Outline the monthly report with the monthly marketing report template.
- Summarise for the owner. In a few sentences: the band, the constraint, the three things that will happen first and the number you expect to move first.
Evaluation criteria
| Criterion | What a strong answer shows | Common gap |
|---|---|---|
| Audit scoring | Gates scored first; the noindexed product pages drive a red band; every row has evidence | Scoring tool warnings at face value, or treating speed as a gate |
| Constraint and sequence | Technical foundation named as the constraint, with content and links sequenced behind it by dependency | Proposing new content while the best product pages cannot be indexed |
| Technical backlog | Template-level tickets with example URLs, expected behaviour and a verification step, ordered by value and effort | Page-by-page tickets, or a list of issues without a definition of fixed |
| Content map | One owner per cluster; town pages consolidated or made genuinely local; the blog and FAQ conflict resolved; orphans linked or retired | New pages added without checking what already competes |
| Link plan | Reclaims the redirected press links, leaves the directories alone, targets relevant sources such as heritage and flood-resilience organisations | Routine disavowing, or asking for keyword anchors |
| Measurement | KPI chain to quote requests, non-brand segmentation, baselines from the same period last year, annotations for every release | Reporting total traffic or average position across all queries |
| Realism | The plan fits the developer's days and the compliance review, and says what is deferred | Five pillars run at full speed by a team of two |
| Owner summary | Plain language, a decision requested, the first indicator to watch and when | A technical summary the owner cannot act on |
A strong submission also explains its trade-offs: what was left out of the quarter and why, and what evidence would change the order. A good roadmap for this brief treats SEOImproving visibility in unpaid search results. as a dependency chain rather than a list of tactics.
Submission checklist
When you have finished, review your roadmap against the evaluation table, then return to the intermediate SEO level to mark the level complete.
