SEO · Search engine optimisation
The unglamorous layer, checked properly.
Can a search engine read, index and rank this page?
Classic search still decides most of what reaches you, and most of what breaks it is a rule nobody remembers adding. We read what your server actually sent, not what your CMS believes it sent.
77checks, grouped by what they inspect
How this usually goes wrong.
- The page is fine and the directive is not
- A canonical pointing at the wrong URL, a noindex left over from staging, a redirect chain that loses the link equity. None of these show up by reading the page.
- The content only exists after JavaScript runs
- We read the page the way a crawler that runs no JavaScript does, and tell you how many words survive that.
- The structured data is present but empty
- A schema block with the right type and no usable values passes most validators and tells an engine nothing.
What happens after we find it.
Titles, meta descriptions, canonicals, heading structure, image alt text and the sitemap are all derivable today. When a finding names a file we can write the change for, it arrives as a pull request rather than a line in a report.
Reading a rule tells you what the file permits. It does not tell you the page was crawled, indexed or ranked, and no check here claims otherwise.
Questions, answered plainly.
Do I need to connect anything for these to run?
Most run from the crawl alone. Some need a connection you make yourself, such as Search Console for ranking data or a backlink feed for off-page. Every check names what it needs, and a check we could not run is reported as not checked rather than as a pass.
How is this different from a normal SEO audit tool?
The findings are the ordinary ones. What is different is what happens next: where we can derive an exact file change, we open a pull request on your repository with the change and the evidence, instead of leaving the work with you.