Services Technical SEO and site speed optimization
Technical SEO and site speed
Faster pages that search engines read properly.
I audit how your site loads and how search engines read it, then fix the problems where they live: in the Webflow project or in your codebase. Speed, Core Web Vitals, indexing, metadata, structured data and redirects, with a before-and-after report for every page I touch.
Most technical SEO problems I find aren’t exotic: the biggest image on the page loading last, a staging site that got indexed, redirects that chain into each other, the same title on fifty pages. They take little time to fix once someone looks, and they cost rankings for as long as nobody does.
What a technical SEO audit covers
- Crawling and indexing: robots.txt, the sitemap, noindex tags, canonical URLs, and staging or preview domains that should never reach Google.
- Site structure: internal links, orphan pages, and how many clicks the important pages are from the home page.
- Metadata: a unique title and description on every page and every CMS item, and Open Graph images for sharing.
- Structured data: JSON-LD for the organisation, services, articles, products or FAQs, validated.
- Redirects and errors: 301s for old URLs, no redirect chains, no internal links to 404s.
- International sites: hreflang between language versions and a sitemap that lists them.
- Speed and Core Web Vitals, measured on a throttled phone connection and on real visitors.
Speed and Core Web Vitals
Google measures three things on real visitors: how long the main content takes to appear (LCP), how quickly the page reacts to a tap or click (INP), and how much the layout jumps while it loads (CLS). On almost every site, the causes are the same few: images larger than their slot, fonts from a third-party server, scripts that load before the content, too much JavaScript, and no caching in front of the server. I fix them in order of impact and measure again after each step.
Technical SEO on a Webflow site
In most Webflow audits I do, Webflow isn’t the problem; what was added on top is. The usual fixes:
- Uploading fonts to Webflow instead of loading them from Google, which also removes a privacy issue for visitors in the EU.
- Moving chat widgets, heatmaps and pixels out of the page settings, or loading them after the content.
- Rebuilding interactions and Lottie animations that run on load and block the first paint.
- Making sure the largest image above the fold isn’t set to load lazily.
- Keeping the webflow.io staging domain out of Google, and filling in SEO fields on every CMS template.
- Setting up hreflang and per-language sitemaps on sites that use Webflow Localization.
Technical SEO on a custom-code site
Sites built in code have more room to be fast and more ways to go wrong. The usual fixes:
- Rendering: making sure the content is in the HTML the server sends, with server rendering or static generation in Next.js or Astro, instead of being built in the browser.
- JavaScript weight: splitting bundles, removing unused libraries, and keeping interactive code to the parts that need it, which is where most INP problems come from.
- Images: responsive sizes and modern formats (AVIF, WebP), with width and height set to stop layout shifts.
- Server and caching: compression, long cache headers on static assets, and a CDN in front of the site.
- Metadata and sitemaps generated from the same data as the pages, so they never drift apart.
This site as an example
This site is built in Astro and follows the same rules: images sized for their slot, fonts served from the same domain, no third-party scripts, and nothing that moves before the content is visible. It scores 99 or 100 in every Lighthouse category on mobile.
When optimization isn’t worth paying for
If your pages score in the 70s or above and Search Console says your Core Web Vitals pass, chasing a perfect score will rarely move your rankings. Money spent on better pages and better content does more. I’ll tell you which side of that line your site is on before you pay for anything.
“Very responsive and pro-active.”
Related work
Live sites
Questions I get asked
What does a technical SEO audit include?
Crawling and indexing, site structure and internal links, titles and descriptions, structured data, redirects and broken links, page speed and Core Web Vitals, and mobile usability. Every finding comes with its fix and its priority, so you know what to do first.
Do you fix the problems or only report them?
I fix them. On Webflow I work inside the project; on custom code I make the changes in your repository, and you get a short report of what changed and what it did to the numbers.
Does page speed affect Google rankings?
Yes, but as a small factor. Core Web Vitals decide close calls between pages of similar quality; speed matters more for how many visitors stay and convert than for where you rank.
Can a Webflow site score 100 on PageSpeed?
Yes, on lean pages without heavy third-party scripts or background video. Most well-built Webflow pages land in the 90s on mobile, and that is enough: Google ranks with Core Web Vitals measured on real visitors, not with the Lighthouse score.
Is my JavaScript framework hurting my SEO?
Only if the content isn't in the HTML Google receives. Next.js and Astro render pages on the server by default; a React app that builds everything in the browser can hide content and slow down indexing, and server rendering or static generation fixes it.
What do you need from me to start?
Access to the site, meaning editor access to the Webflow project or the repository and hosting for custom code, and read access to Google Search Console. If Search Console isn't set up, that is the first task, because it shows the problems real visitors have.
Something not answered here? Ask it on the call.
Book a call