Technical SEO: What to Fix First and When to Stop

This guide is for the owner or marketing lead of a small or mid-sized business website, usually on Shopify, Wix or WordPress, who has an audit report with hundreds of warnings and a developer or freelancer with a few hours to spare. You don't need to know what every warning means. You need to know which fixes go first, and when to stop.

Below is a default order for those fixes, the few situations that change it, and a one-hour check that tells you whether technical SEO is your problem at all. On hosted platforms, the platform already handles much of what an audit flags.

What order should technical SEO fixes go in?

Fix whatever stops a visitor from becoming a customer first, then whatever stops Google from seeing your money pages, then the problems that slow either down. Cosmetic warnings go last, whatever the tool's severity label says.

Items 1–4 are blockers. Items 5–7 are constraints, and they matter more as the site grows. Item 8 is housekeeping. When an agency's report leads with item 8 because it produced the most warnings, the report is sorted by count, not by impact.

What could change the order?

Five situations reorder the list:

• Large catalogues. On a store with thousands of products and filter combinations, items 5 and 6 move up to sit just behind the blockers. One bad category template affects most of the site.
• English and Arabic versions, or many location pages. Item 6 moves up. Google can pick the wrong language version as canonical across a whole section, and a sample of five URLs won't show it.
• Custom JavaScript builds. If the site is a headless or single-page app, check that the main text and links appear in the rendered HTML. That check belongs at item 2.
• A recent migration or redesign. Redirects from old URLs go to item 2. Every old URL that earned traffic needs a direct redirect to its closest new equivalent.
• No traffic yet. If nobody visits, item 1 has nothing to protect. Start at item 2.

When should you stop doing technical SEO?

Stop once the four blockers are ruled out and your money pages show as indexed in Search Console. On Shopify, Wix or managed WordPress, the platform already handles hosting, HTTPS, sitemaps and most canonical tags. What it can't stop is a setting someone switched on and forgot.

Here is the one-hour check:

1. Search visibility settings (10 minutes). WordPress: Settings › Reading, confirm "Discourage search engines from indexing this site" is unticked. Wix: in SEO settings, confirm the site and each money page are set to be indexed. Shopify: Online Store › Preferences, confirm password protection is off.
2. robots.txt (5 minutes). Open yourdomain.com/robots.txt. If a line says Disallow: / under User-agent: *, or blocks a folder your money pages live in, that's a blocker. On Shopify, also check whether the robots.txt template has been edited.
3. Indexing (20 minutes). In Search Console, run URL Inspection on your five to ten most valuable pages. Each should say "URL is on Google", with "Crawl allowed?" set to Yes. Then scan the Pages report for server errors, redirect errors and "Blocked by robots.txt".
4. Actions and tracking (20 minutes). On a phone, submit each form, start a checkout and tap the WhatsApp and call buttons. Confirm each one reaches a person or an inbox, and appears in GA4 as a key event.
5. One domain (5 minutes). Load the http, https, www and non-www versions of your homepage. All four should end on the same URL.

If all five pass and you still aren't ranking, more technical work is unlikely to change that. The usual causes are pages too thin to answer the search, and too few other sites linking to yours. Google's own guidance on helpful, people-first content focuses on what the page says. Put the developer hours into a better service page, then go after links from directories, partners and the press.

If you run English and Arabic versions or many location pages, add ten minutes for item 6. In URL Inspection, compare the user-declared and Google-selected canonical on a few pages from each language and location set. A crawler will still show warnings after all this. Leave them for the monthly sweep in item 8.

How do you tell a real issue from a tool warning?

Reproduce it on a live URL that matters, and name the evidence source. Treat every tool warning as a lead to investigate.

• Indexing: Search Console URL Inspection, comparing the live test with the indexed version.
• Crawling: a crawler such as Screaming Frog, run with JavaScript rendering on and then off.
• Performance: PageSpeed Insights, reading the field data (CrUX) first and the lab score second. Web Vitals defines the three measures: LCP, INP and CLS. Name the cause in the ticket, for example "the hero image delays the main content on mobile service pages".

A finding without one of these attached is an opinion.

Keep crawling, indexing and ranking apart. A page Google can fetch isn't necessarily indexed, and an indexed page doesn't necessarily deserve to rank. If a page passes the technical checks but says little, hand it to whoever writes your content.

Where to start

Run the free audit at the top of this page. It checks your homepage and a few linked pages for page speed (real-visitor data where Google has it), meta description and headings, whether robots.txt responds and a sitemap is declared, and which analytics and ad tags are installed. It doesn't read your robots.txt rules, check for noindex or test your forms, so the rest of the one-hour check still needs doing by hand. If the blockers come back clean and the ranking problem is content and authority, that's the work our SEO service is set up for.