Keeping a site fast, current and crawlable after launch.

Implementation is where a recommendation becomes a change on the site: a template edited, a redirect added, structured data written, a canonical corrected. Google's documentation is mostly about what a correct result looks like, and it points to tools for checking. The URL Inspection tool in Search Console lets you check how Google sees a specific URL. Google's structured data introduction advises checking markup with the Rich Results Test during development and monitoring it afterwards with the rich result status reports.

The site move guide shows the same habit for redirects: test them with the URL Inspection tool for single URLs, or with command line tools or scripts for large numbers. Google's JavaScript troubleshooting guidance likewise suggests testing how Google crawls and renders a URL when content fails to appear, and collecting and auditing the JavaScript errors that users, including Googlebot, encounter.

The point is that a change is not finished when it is deployed; it is finished when it has been checked on the live site. We cover technical SEO implementation: templates, redirects, structured data and tooling built by us where that is faster than waiting on a queue, or written up as tickets with the fault, the evidence, the fix and the acceptance test for your developers. Releases are checked before and after launch. See implementation and QA and our article on audit findings that get implemented.

Google's Core Web Vitals page describes three metrics: Largest Contentful Paint for loading (aim for within 2.5 seconds), Interaction to Next Paint for responsiveness (under 200 milliseconds) and Cumulative Layout Shift for visual stability (under 0.1). Google highly recommends good Core Web Vitals, and says they align with what its core ranking systems seek to reward. Its page experience guidance adds that site owners should not focus on only one or two aspects: secure serving, mobile display and intrusive interstitials are on the same list.

Scalability has a search side too. Google's crawl budget guide says the crawl capacity limit rises when a site responds consistently with stable or improving response times, and falls when the site slows down or returns server errors or rate-limiting signals such as 429. The same guide is written for very large or rapidly changing sites, and says other sites do not need it. For those sites it says that if Google can load and render pages faster it may be able to read more content, and it lists optimising server response times, supporting HTTP caching with 304 responses and avoiding long redirect chains. Adding server resources is named as one way to raise crawl budget when server capacity is the limit. The site move guide also warns that Google crawls more heavily after a move, so servers need capacity.

We treat performance as budgeted, not hoped for, so it is decided at the start of a build. Performance is one input among many: most serious technical problems sit in crawling, indexing, rendering and architecture, which is why Core Web Vitals are not the whole story in our Technical SEO work.

A site keeps changing after launch: new templates, plugins, content types, hosting, integrations. Each change can affect crawling or indexing, and Google's guide to debugging traffic drops is a reminder of how. It lists technical issues, such as server availability, robots.txt fetching, page-not-found errors and a misplaced noindex tag, among the main causes of a drop, and points to the Crawl Stats and Page indexing reports to find them. It also notes that a noindex problem shows as a slower drop, because it depends on Google recrawling the page.

The same guide says some changes take effect in days while others take months, and that there is no guarantee a change will have a noticeable impact. Our approach to measurement reflects this: we do not promise rankings or traffic numbers, we set out the opportunity and the evidence, and measure against it.

Ongoing technical development is part of our ongoing SEO work, alongside technical SEO implementation, performance and scalability, and SEO QA that checks releases before and after launch so regressions are caught early. Google's sitemap guide adds a small recurring detail: it uses a sitemap's lastmod value only if it is consistently and verifiably accurate. It is a loop rather than a one-off checklist: investigate, diagnose, prioritise, implement, measure, iterate. Consultancy differs because it adds expertise to your team, whereas ongoing SEO means Cultured Digital runs the programme; many clients move between the two. See ongoing SEO.