The technical basics search engines still check
Before content or backlinks matter at all, a site needs the basics right, and we still find these broken on a meaningful share of the sites we audit. Clean URLs — /services/roof-repair rather than /page?id=4821&cat=2 — tell both users and crawlers what a page is about before they've read a word. One H1 per page, matching the actual topic of that page, gives search engines an unambiguous topic signal instead of competing headlines. Semantic HTML (real <nav>, <article>, <h2> tags instead of a soup of styled <div>s) makes a page's structure legible to crawlers and assistive tech alike. And a working sitemap.xml plus a sane robots.txt make sure the pages you want indexed get found, and the ones you don't (staging pages, thank-you pages) get skipped.
None of this is exotic. It's also exactly the layer that generic website builders and cheap templates get wrong most often — a page-builder plugin bolted onto a template rarely produces clean markup underneath the visual polish, which is one reason we push clients toward a properly built website design rather than a stacked-plugin approach when SEO actually matters to the business.
Speed and Core Web Vitals
Google measures three specific things under the Core Web Vitals umbrella: how fast the main content appears (Largest Contentful Paint, ideally under 2.5 seconds), how responsive the page feels to the first interaction, and how much the layout jumps around while loading (Cumulative Layout Shift, ideally under 0.1). A page stuffed with unoptimized images, render-blocking scripts and auto-playing carousels will fail these even if the content itself is excellent.
The fixes are unglamorous but effective: compress and properly size images, lazy-load anything below the fold, defer non-critical JavaScript, and reserve space for ads or embeds so they don't shove content around after it's rendered. We've seen sites move from a 6+ second load time to under 2 seconds purely by fixing image handling, with no design changes at all.
Speed isn't just a ranking signal — it's a conversion one. A one-second delay in load time measurably increases bounce rate on mobile, independent of anything Google does with that data.
Mobile-first indexing, taken literally
Google has indexed the mobile version of a page as the primary version for years now, which means a desktop-only design flaw — text that's readable at desktop width but crammed at 375px, a menu that only works with a mouse hover — is an SEO problem, not just a UX one. Test the actual mobile rendering, not a shrunk browser window: tap targets, font size, and whether critical content (like a phone number or booking button) survives the smaller viewport intact.
Internal linking that actually helps
Internal links do two jobs: they help visitors find related content, and they tell search engines which pages on your site matter most and how topics relate. A site with a hundred orphan pages — each reachable only through the sitemap, never linked from anywhere else — is telling Google those pages aren't important, whether that's true or not. The fix is deliberate: link from high-traffic pages down to relevant deeper pages, and cross-link related content within the same topic (the way this article links to related guides at the bottom) rather than relying purely on the main navigation menu.
Schema markup: the quiet multiplier
Structured data (schema.org markup, usually as JSON-LD) doesn't directly boost rankings on its own, but it removes ambiguity — it tells a search engine explicitly "this is a FAQ," "this is a local business with these hours," "this is a blog post published on this date." That clarity is what unlocks rich results like star ratings, FAQ dropdowns and map-pack eligibility, and it's increasingly what AI answer engines lean on when deciding what to cite.
Content structure and AEO readiness
Technical SEO gets a page crawlable and indexable; content structure gets it actually chosen. One topic per page beats one bloated page trying to cover everything, and answering the core question in the first few sentences beats building up to it after three paragraphs of preamble. This is also exactly the structure that feeds into answer engines like AI Overviews and ChatGPT search — if you want the fuller playbook on that layer, our AI Overviews guide goes deeper into it. Think of AEO-readiness as the natural extension of good SEO structure, not a separate discipline you bolt on later.
In practice, that means writing headings as the actual question a person would type, resolving it directly underneath, and only then adding nuance, caveats or a longer explanation. Both traditional search and AI-generated answers reward the same shape of content, which means building for SEO and building for AEO are no longer two separate projects with two separate content plans.
Common mistakes that quietly cap rankings
Beyond the checklist items above, a handful of recurring mistakes show up again and again in the audits we run. Duplicate or near-duplicate title tags across dozens of pages, usually left over from a template that never got customized per page. Thin, auto-generated location pages built purely to target a keyword, with no unique content, which search engines increasingly filter out rather than reward. Broken internal links pointing to pages that were renamed or removed during a redesign, quietly wasting crawl budget and passing visitors to a dead end. And images with no alt text at all, which is both an accessibility failure and a missed opportunity for image search visibility.
None of these require a rebuild to fix — they're the kind of issue a proper technical audit catches in an afternoon, and fixing them is often the fastest ranking improvement available to a site that's otherwise been stagnant for months.