Missing from Google
Pages you expect in Google are missing, or show “Crawled, currently not indexed”.
Technical SEO consulting that keeps your site discoverable and performing. I focus on crawling, indexation, site architecture, rendering and structured data, so search engines can find, understand and confidently surface your pages.
Crawled. Indexed. Rendered. Described.
If any of these feel familiar, a technical SEO audit is the place to start.
Pages you expect in Google are missing, or show “Crawled, currently not indexed”.
Clicks or rankings changed and nobody can say why.
A migration or redesign is coming and you want it checked first.
Your developers have a long list of warnings and no sense of which ones matter.
Recommendations sit in a document and nothing changes on the site.
Changes went live and nobody checked what actually happened.
Five steps take your site from a crawl to a checked result.
I crawl the site with Screaming Frog, then check the pages that matter by hand.
Robots rules, sitemaps, canonicals, redirects, status codes, site architecture and internal links are checked. Every finding comes with evidence.
Issues are ranked by what they stop search engines from doing, so cosmetic warnings do not crowd out the fixes that matter.
Each fix is written so a developer can act on it. I work with your developers directly, including on modern and headless CMS builds.
After the changes ship, I crawl again to check what was fixed and what was not.
Six areas decide whether search engines can reach, read and trust your pages.
Can search engines reach the pages that matter, and are they told the right things on the way?
Are the right pages in Google, and the wrong ones kept out?
Is the site easy to move through, with every important page linked from somewhere sensible?
Do pages load and display in a way search engines can read, including content built with JavaScript?
Does markup describe what is on the page, so search engines understand it with confidence?
Before and after a redesign or move, are old addresses mapped to new ones and nothing lost on the way?
Your technical SEO review
Technical SEO
Every issue with the pages affected and the evidence, ranked by what it stops search engines doing.
Each fix described so a developer can act on it without a call.
A second crawl after the changes ship, to confirm what worked.
Every issue on the list carries the same five parts.
You want to know whether search engines can reach and understand your pages.
You want a redesign or move checked before and after launch.
You want clear, actionable fixes, not a long list of warnings.
A checked result you can follow, and plain talk about what it can and cannot do.
Straight answers on how the work runs and what it covers.
I look at how search engines can explore, access and understand your site. That includes crawling, indexation, site architecture, rendering and structured data. I then prioritise the issues and give clear, practical fixes. Every finding comes with evidence, and the work ends with a re-crawl to confirm what changed.
A technical SEO audit checks whether search engines can reach, read and understand your site. I crawl the site with Screaming Frog, check the pages that matter by hand, and look at robots rules, sitemaps, canonicals, redirects, status codes, site architecture and internal links. You get a prioritised list of what is wrong, the evidence for each issue and the fix.
It depends on your site, your competition and how much needs to change, so I do not give a fixed date. Fixes are usually crawled and assessed over weeks, and results tend to build over months rather than days. What I can commit to is a priority order, so the changes most likely to matter happen first, and a re-crawl that shows what changed.
An automated report lists every warning it can find, usually in the order the tool produces them. A human review checks which issues actually stop search engines doing their job, ranks them by impact and writes each fix so a developer can act on it. Cosmetic warnings stay at the bottom of the list instead of crowding out the fixes that matter.
After the changes ship, I crawl the site again with the same settings. It shows what has been fixed, what has not, and whether the release created any new issue. It turns a list of recommendations into a checked result.
Screaming Frog is the main crawler, alongside manual checks of the key pages and your search performance data where it is available. The tools are only a means to the review. The value is in deciding which findings matter and what to do about them.
Yes. Each fix is written so a developer can act on it, and I work with your developers directly, including on modern and headless CMS builds. I can answer questions while the changes are built and check the result afterwards.
The service delivers the prioritised list and developer-ready fixes, and checks the outcome with a re-crawl. Your developers or site team make the changes, and I work with them as needed.
Good moments are before a migration or redesign, after an unexplained drop in clicks or rankings, when pages you expect are missing from Google, or when your developers have a long list of warnings and no sense of which ones matter. It is also worth repeating regularly, because sites change.
It removes barriers that stop search engines reaching and understanding your pages, which is a necessary base. It does not guarantee a ranking, a traffic figure or a date, because rankings also depend on content, competition and links. The re-crawl shows what changed on the site, so you can judge the work on evidence.
Your website address and your goals. If a migration or redesign is planned, the dates help. Access to your search performance data is useful, but the work can begin without it.
Crawl access and clear pages matter for AI answers too. Read about AI search optimisation (GEO and AEO).
Once the site can be crawled, every keyword needs a page with one clear purpose. Read about SEO content strategy.
After the fixes ship, your search data shows what changed. Read about SEO reporting and analytics.
Send your website URL and goals to review crawl health, indexing, rendering and core technical setup.
Last updated 4 November 2026