I picked up a project where the team had done real work on their search strategy, keyword research, page copy, a content plan, and were frustrated that none of it was moving. Impressions were flat. New pages were not showing up in results at all.
The cause was one line in a config file. Their sitemap was generated dynamically on every request, and under load it was timing out. Search Console had marked it as unreadable and quietly stopped trusting it. Google was not ignoring the content; it had never been told the pages existed.
The order of operations
Search work has a dependency chain, and most teams start in the middle of it.
- Google can reach the pages. They return a
200, they are not blocked inrobots.txt, and there are internal links to them. - Google knows the pages exist. A working sitemap that lists them, submitted and readable in Search Console.
- Google understands what each page is. Clean titles and descriptions, sensible URLs, structured data where it fits.
- The page deserves to rank. It genuinely answers the search it is targeting.
- Then keywords, content and links.
Steps four and five are where the SEO industry spends its time, and they matter, but they do nothing while steps one to three are broken. You can write the best page on the internet for a query and it will not rank if the crawler cannot fetch it or was never pointed at it.
Fixing the plumbing
On that project the fix list was short and entirely technical:
- Make the sitemap reliable. Either serve it as a static file, or cache it so it is generated at most once an hour rather than on every hit. Then resubmit it.
- Request indexing by hand for the homepage and key pages while the sitemap recovers, using the URL inspection tool.
- Regenerate the sitemap when content changes, so new pages are listed within minutes, not on the next deploy.
- Spot-check that the pages actually return
200. A sitemap full of URLs that error is worse than no sitemap.
That is a day of work, and until it is done, the commercial side, keywords, copy, outreach, is spending effort the crawler cannot see.
The takeaway
Before you brief anyone to write for search, or pay for a content plan, confirm the basics: pages reachable, sitemap working, Search Console clean. It is unglamorous, it is quick to check, and it is the difference between search work that compounds and search work that disappears.
This is build-time plumbing, and it is part of how we approach search on every project.

Written by
Steven Noble
Steven Noble is the founder of Graphics Cove, a senior full-stack engineer with 19 years building web products for startups and established companies. He writes about engineering, delivery and running a technical practice.