We check whether search engines index your whole website and how fast it loads for real visitors, and we fix what we find. After that we monitor that it stays that way.
- Indexingrobots.txt, sitemap, canonicalschecked
- Language versionshreflangchecked
- Core Web VitalsLCP too high on mobilefix planned
- MonitoringUptime and Search Consoleactive
If something gets worse, we get in touch with the cause and a proposal.
What we check
For indexing we look at robots.txt, sitemaps, canonicals, redirects and status codes. Pages that should not appear in search get a noindex. If the site has several languages, we check hreflang and how the language versions link to each other.
Load times come from real visits, measured as Core Web Vitals (LCP, CLS, INP). A test on your own computer is not enough on its own. We also check the schema.org data for your organisation, services and articles, so that the preview in search is right.
What we find, we fix in the code or in the server configuration. If your own team wants to take it on, we write you a list of what to change where.
Examples from our work
- When Search Console reports pages as Crawled, currently not indexed or as Page with redirect, we find out why.
- We keep staging and CMS hosts out of the index.
- If the Largest Contentful Paint is slow, we look for the cause.
- In Lighthouse runs we compare the transferred bytes as well as the score.
Monitoring
- Website uptime and certificate expiry
- Search Console: indexing errors and drops in clicks
- Load times after every release
If something gets worse, we get in touch with the cause and a proposal for what to do.
We teach this too
Technical SEO and monitoring are also subjects we teach. For our own website, a script checks titles, descriptions, canonicals and hreflang on every build, before anything goes live.
What we do not do
We do not write copy for search engines, build links or run paid ads.