SEO Optimisation: Why the Technical Stuff Actually Matters
A site that looks polished in a browser can be virtually invisible to Google. The design is fine. The content is there. But underneath, the crawl path is broken, canonical tags are missing, and half the page is rendered by JavaScript that Google never waited around to process. That gap, between what a visitor sees and what a search engine actually reads, is where most ranking problems live. Closing it requires going under the bonnet, not tweaking the homepage copy.
On this page
- Google recrawls after fixing crawl issues can take two to six weeks to show in rankings.
- A page returning a 200 status can still be excluded from Google's index.
- Core Web Vitals measure LCP, CLS, and INP as part of Google's ranking signals.
- Yorkshire Design carries out full technical SEO audits covering crawl path, canonicals, and Core Web Vitals.
Last updated
What Google Actually Crawls
Google doesn’t visit your site the way a person does. Googlebot follows links, reads HTML, and decides how much time to spend on your domain based on something called crawl budget. If your site wastes that budget on low-value URLs, parameter-generated duplicates, or blocked resources, the pages you want ranked get less attention.
Rendering is a separate problem. Modern WordPress sites often rely on JavaScript to build the page in the browser. Googlebot can process JavaScript, but it doesn’t always do so immediately, and a page that requires client-side rendering to show its main content can sit in a queue for days before Google reads it properly. Your visitors see the full page. Google may have indexed an empty shell.
The practical result is that indexation, the step where a page enters Google’s index, can fail without any obvious sign. The URL returns a 200 status. The page loads fine in a browser. But Google chose not to include it, or included an incomplete version, and you won’t know unless you check the URL Inspection tool in Google Search Console and look at the rendered HTML.
The Gap Between a Pretty Site and a Ranking One
Visual quality and search performance are separate problems, and a site rebuilt on a premium theme with professional photography can perform worse in search than a plainer one if the underlying code is heavier and slower.
Core Web Vitals are the measurable bridge here. Google publishes the Core Web Vitals metrics as part of its page experience signals, and they measure things visitors feel even if they don’t consciously notice them. How quickly the largest element on screen loads (LCP). Whether the page shifts unexpectedly as it renders (CLS). How fast it responds to a first interaction (INP). A beautifully designed page with a 4.8-second LCP is failing on a metric Google explicitly uses in its ranking signals, and the design team won’t know, because they’re judging from a fast laptop on a wired connection.
These scores show up in real-world data and they’re almost always fixable with changes that have nothing to do with how the site looks.
Where Most Sites Lose Rankings Without Knowing It
The faults that cost rankings tend not to be dramatic. They accumulate across a site until the combined weight drags performance down. On WordPress sites in particular, a few problems come up repeatedly.
Duplicate content
Category pages, tag archives, author pages, and paginated URLs often serve near-identical content with no signal about which version to rank. Google picks one, and it may not be the one you wanted.
Conflicting or absent canonical tags
A canonical tag tells Google which URL is the definitive version of a page. When they’re absent, auto-generated wrongly, or contradicted by a redirect, Google has to make a judgement call that won’t necessarily favour your preferred URL.
Render-blocking scripts
A plugin that loads a full JavaScript library on every page, even pages that don’t use it, delays the browser from painting any visible content. That delay feeds directly into LCP.
Slow server response
Time to First Byte (TTFB) measures how long the server takes to respond. Shared hosting with no page caching can push this above a second, and a slow TTFB makes every other performance metric worse downstream.
For a concrete example of how these issues compound: this rebuild project involved a site developed on top of an existing theme, which had created custom post type conflicts and styling issues that made a clean crawl path impossible. Once the site was rebuilt properly from the ground up on WordPress, it returned to page one for several competitive terms. The technical foundation was the fix, not the content.
How a Technical SEO Pass Works
A technical audit isn’t a scan followed by a report you put in a drawer. The useful version is a prioritised fix list ordered by what’s hurting performance, starting with anything that prevents indexation and working toward the smaller wins.
The process runs roughly as follows. Crawl the site with a tool like Screaming Frog to map every URL, status code, canonical tag, and internal link. Cross-reference against Search Console to see what Google has indexed and what it’s flagging. Then check Core Web Vitals in the field data, not just the lab scores, because lab scores are estimates and field data is what real users experienced on your pages.
Priority decisions come from impact and effort. A missing canonical on the homepage is more urgent than a slow image on a rarely-visited product page. Fixing a render-blocking script that affects every page load beats tidying metadata on five blog posts.
Measurable change takes time. A Google recrawl after fixing crawl issues might take two to six weeks to show in rankings, and there’s no shortcut to that timeline. You can verify progress in Search Console as coverage numbers shift and previously excluded pages start appearing. For a fuller picture of what this process looks like in practice, the article on technical SEO fixes for WordPress goes into the specific areas to check first.
Get Your Site Checked
If you’re not sure whether your site has these issues, most WordPress sites do. A proper technical look takes time to do thoroughly, but it’s the kind of work that pays back steadily over months as crawling, indexation, and page experience improve together.
Yorkshire Design carries out full technical SEO audits, from crawl path and canonical structure through to Core Web Vitals and server configuration. If you’d like to know what’s holding your site back, get in touch and we’ll tell you plainly what we find.