Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

SEO › Advanced

Capstone: A Forecast-Backed SEO Strategy for a Hardware Retailer

The closing project of the advanced SEO level. You write a year's strategy for an invented hardware retailer with a huge catalogue, a planned sister site abroad and a possible move to a JavaScript front end: technical risks ranked and scheduled first, indexing rules a developer can build, a forecast with ranges and named assumptions, and the monthly operating rhythm and board reporting that deliver it.
Capstone projectAdvanced levelModule 3: Diagnosis, forecasting and the SEO programme6 minUpdated

Brief

Westerby Hardware Supply is an invented hardware and DIY retailer with a catalogue of tens of thousands of products. Organic search has been flat for a year. Over the same period, filter combinations have multiplied, new products take weeks to be found, and the indexing report has filled with duplicates.

Two projects are on the platform roadmap. The first is a site for a neighbouring country in the same language, with its own prices and delivery terms. The second is a proposed move to a JavaScript front end, which the developers favour and which would, by default, render category and product listings in the browser.

The board wants a strategy that says what search will deliver over the year, what it needs from developers and writers, and which risks could undo it. Treat SEO as a dependency chain: the SEO strategy framework asks which of its five pillars is the constraint now, and sequences the work by dependency rather than by enthusiasm.

Inputs and constraints

Illustrative example — not a real result

Westerby Hardware Supply: crawl, index and Search Console

SignalReading
ProductsAbout 38,000
URLs known to the crawlerAbout 2.1 million
Share of crawl requests to filter parametersAbout 64%
Duplicate without user-selected canonicalAbout 640,000 URLs
Median time from product launch to first crawlAbout 25 days
Town delivery pages120 pages, name swapped only; about 70% crawled, currently not indexed
Non-brand organic clicksFlat at about 410,000 a month for twelve months
Share of organic clicksCategories 48%, products 30%, guides 17%, other 5%
Organic conversion rate and average orderAbout 1.6% and £48
Illustrative example — not a real result

Westerby Hardware Supply: priority clusters, team and roadmap

ClusterMonthly searches (cluster)Current average positionRealistic target rangeIntent
Cordless drills74,000114 to 7Commercial
Garden sheds40,500146 to 10Commercial
Bathroom taps33,10093 to 6Commercial
Laminate flooring27,000188 to 12Commercial
How to tile a wall22,20063 to 5Informational

Team: an SEO manager; developer time of about two days a fortnight; one in-house writer plus freelance budget for about six briefs a month; category buyers available for product reviews.

Roadmap: neighbouring-country site planned for the second quarter; JavaScript front end proposed for the third quarter, client-side rendering by default, server rendering possible at extra cost.

Constraints you must work within:

  • Developer time is scarce, so technical work must be grouped into template-level changes and staged releases.
  • The board will not accept a single traffic promise; it wants ranges and the assumptions behind them.
  • Neither launch on the roadmap can be cancelled by the SEO team, but both can be shaped and gated.
  • The strategy must still deliver visible growth work within the year, not only risk removal.

Task

  1. Diagnose the programme. Rate each of the five pillars in the SEO strategy framework and name the current constraint with its evidence. Score the gates and the duplicate, crawl efficiency, JavaScript rendering and international rows of the technical SEO audit scorecard, and say what the Crawl Budget evidence means for a catalogue of this size.
  2. Rank and schedule the risks. Rank the faceted crawl, the town pages, the new country site and the front-end move by likelihood and damage. Schedule them before growth work, using the site migrations guide and the website migration checklist for the two launches. State the conditions the front-end move must meet before SEO signs it off, drawing on the bathroom retailer redirect map exercise.
  3. Write the indexing rules. Set tiered rules for filters as in the faceted navigation guide and the fabric shop filter exercise. Decide what happens to the town pages. Specify hreflang for the two country sites: generation, validation, self-canonicals and what makes each edition distinct.
  4. Forecast the priority work. For each priority cluster, run the SEO traffic estimator for keyword prioritisation at the low, middle and high end of the realistic target range, with the conversion rate set by intent. Convert to orders and revenue, add the expected value of faster product indexing as a separate, clearly labelled assumption, and present ranges with every assumption named.
  5. Define the operating rhythm. Turn the plan into a monthly cycle using the SEO content operations playbook: planning against capacity, briefs with the content brief template, review by buyers, publishing and linking, a refresh queue and quarterly maintenance. Name an owner for every stage and every developer request.
  6. Design the measurement and the drop protocol. Choose board-level KPI figures that run from indexed priority pages to organic revenue, segmented by page group and market, with an annotation log. Write the protocol for diagnosing a drop, in the order used in the recipe publisher rankings drop exercise. Outline the monthly report with the monthly marketing report template.
  7. Summarise for the board. In plain language: the constraint, the risks being removed first, the forecast range, what is needed from developers and writers, and the first figure that should move.

Evaluation criteria

CriterionWhat a strong answer showsCommon gap
Risk firstRanks migration, rendering and indexing risks and schedules them before growth workLists every technical issue at equal priority
Indexing rulesSets clear rules for facets and regional pages that a developer could implementLeaves duplicate and thin URLs to the search engine to sort out
ForecastForecasts the priority work with ranges and named assumptions, using the traffic estimatorPromises a single traffic number with no assumptions
Operating rhythmDefines the monthly cycle of planning, briefs, publishing, refreshes and reporting with ownersA one-off project plan with no ongoing cadence
MeasurementReports KPIs the board understands and how a drop would be diagnosedReports rankings only

A strong submission notices the order the evidence imposes. With most crawl requests spent on filter parameters and new products waiting weeks, indexing is the constraint, and content written now would queue behind the duplicates. The front-end move is the largest single risk: a strong answer makes server rendering of listings, real links, initial-HTML titles and canonicals, and a full redirect and rendering test on staging the conditions of SEO sign-off, and refuses to let it share a release with the country launch.

The forecast earns trust by what it admits. A strong answer shows how sensitive each cluster is to the position assumption, keeps the indexing benefit separate from the content forecast, and says when the curve will be replaced by Westerby's own click-through data from Search Console.

Submission checklist

0/8

When you have finished, review your strategy against the evaluation table, then return to the intermediate SEO level if any reporting or keyword mapping basics need a second look before you mark the level complete.

Pages this lesson applies

Terms used on this page

Also related

Related