When the content is right and the rankings are not

A content programme runs for fourteen months. Articles go up on schedule, the set of pages is sound, and the voice is steady across every piece. The rankings climb for the first six to eight months, then flatten. A technical audit of the site finds:

• Pages taking six seconds to load on a phone
• Errors stopping Google from reading forty percent of the pages it has found
• No schema on any page
• Web addresses laid out by the website's default settings, not by the subjects the content was built around

The content did not fail. The site under it capped how far the rankings could climb, and nobody told the owner the cap was there until the rankings had been flat for six months.

What most SEO agencies leave out

Technical SEO is the part most agencies treat as optional for smaller businesses. The thinking goes that technical problems belong to big sites: thousands of pages, in-house developers, crawl budgets worth managing. An owner running a twenty-page WordPress site is told the content is what counts. The advice is not wrong; content does count. What it leaves out is this: a slow, badly built site limits what any content can do, however good the writing.

Google cannot rank what it cannot read. A page taking six seconds to load on a phone is marked down on speed before Google reads a single word of it. A page with no schema gives search engines nothing in code to say what the page is, who wrote it, or what subject it covers. A site whose web addresses fight the order of its content sends a mixed signal about what it is even about. These are not advanced problems. They are the floor below which no content does its best work, and they show up on small business sites as often as on big ones.

How we build

We build on Next.js and Vercel: pages search engines can read and list without trouble, served fast enough to pass Google's speed checks on a phone, with a place to manage content that gives full control without touching the code. The setup is not a personal taste. It is the base managed publishing needs to run with no gap between the plan and what goes live.

Schema, the bit of code that tells search engines what each page is about, goes on as standard on every build. Web addresses are laid out to match the order of the subjects before the first page is built, not patched on after the content is live. Page speed is measured before launch and fixed in the build, not flagged six months later in a report nobody acts on.

For clients moving off WordPress or another old platform, the build includes a full set of 301 redirects. A 301 redirect tells search engines a page has moved for good and carries its ranking from the old web address to the new one. Without it, moving the site wipes out whatever standing the old site had built. With it, the move protects the rankings the content has already earned.

What the technical audit covers

A technical audit is not a separate job done before the content work starts. It is the first pass of the onboarding audit, running next to the keyword mapping and the brand voice work, because the state of the site decides what the content can do before a single article is written.

The audit measures page speed, whether Google can crawl the site, how the web addresses are laid out, whether schema is in place, how the site shows on a phone, and the core speed and stability scores. For a business on an existing platform, it shows what has to change before the retainer begins. For a business with no site, or one that cannot support managed publishing, it spells out what the build has to include.

Most owners reach this stage having never seen a technical audit of their own site. The findings are rarely dramatic. A missing sitemap, a robots.txt file blocking pages from being read, image files big enough to slow every page they sit on. The problems are fixable. The harm they have done for months or years, with nobody measuring it, is the part worth taking in.

What changes when the technical foundation is right

A clean technical base does not promise strong rankings. It lifts the cap holding them down. A business spending fourteen months on content running on a broken site has been paying for results the site was blocking. The content was doing its job. The site was not.

The upshot is content growing the way it was meant to. Pages get listed properly. Load times pass the bar Google uses to judge the phone experience. Schema tells search engines and AI tools what each page is, who made it, and which set it belongs to. The signal is clean because the site is clean.

For an owner who has watched a content programme go flat for no clear reason, the technical audit tends to land the same way: the problems were there from the start, the content was fighting them the whole time, and fixing them costs less than the months spent wondering why the rankings stopped moving.