A site can look perfect in a browser while search engines render an incomplete mobile version or select the wrong URL. We change the code ourselves where we have access, record each change and confirm the outcome in Search Console instead of handing over a list of warnings.
01
Canonicals are not an overlap cure
Canonical tags suit parameter variants, print versions and trailing-slash duplicates. They are the wrong tool for two pages serving genuinely different needs. When two services compete for one query, the fix is usually clearer titles, headings and content boundaries, with internal links pointing consistently to the page that owns each topic.
02
Typical fixes are unglamorous
Most improvements come from ordinary engineering discipline rather than clever tricks:
- Correctly sized, compressed images
- Fonts that do not shift layout
- Third-party scripts loaded only where needed
- Hero content that renders without a slider
03
A dated release log
Every change is logged with its affected URLs. After deployment we inspect those URLs, request recrawling where useful and compare equivalent periods. If the constraints are still unknown, a scoped audit comes first; this service is for when the problem is understood and needs fixing.
04
Agree what a completed fix means
A ticket should name the affected template, the expected behaviour and the test that will close it. For a missing service page, that might mean a successful response, crawlable internal links, the intended canonical and complete mobile content. Google choosing to index it is a subsequent observation, not something a developer can promise at deployment.
We also identify dependencies before editing: who owns DNS, whether the CMS allows template changes and whether an external booking tool can be altered. Work on a preview or staging copy where available, keep a rollback route and check that the inquiry path still works after release. These safeguards keep an engineering change from becoming a new business problem.
05
Mobile first, in practice
Google indexes the mobile version of a page, so content that appears only on desktop can go unseen. Check that headings, service text and internal links exist in the mobile HTML, not only after a tap or scroll that a crawler will not perform. Compare the rendered mobile page with the desktop page for the same URL before changing anything else.
06
Sitemaps and robots files
A sitemap should list the pages you want indexed and nothing else. Utility pages such as intake forms and legal documents usually carry a noindex directive instead of a robots block, so crawlers can read the instruction. Keep both files in step with the site after every release.
