By Taqweem Ahmad | Founder, Dexora Digital | April 2026 | Issue 7
The March 2026 core update finished rolling out on April 8. If your rankings dropped, the diagnosis and recovery path were covered in last month’s newsletter. This month I want to address the more important question.
What does a site that never needs to recover look like?
After 500-plus audits, the pattern is consistent. The businesses that hold and improve through every core update are not the ones with the biggest content budgets or the most backlinks. They are the ones that built the technical foundation correctly and maintained it consistently. Every single time.
Technical SEO is not glamorous. It does not generate case study headlines. But it is the work that makes everything else — content, local SEO, AI search visibility, Google Ads — produce better results with less effort. And it is the work that most businesses neglect because they cannot see it changing on their website.
Content without a technical foundation is traffic that underconverts. Local SEO without a technical foundation is citations that underrank. AI search without a technical foundation is content that gets ignored by crawlers. The foundation comes first. Everything else is built on top of it.
This issue gives you the 30-point technical SEO checklist I run on every new client site before we touch content, links, or ads. It is organized into six categories. Work through them in order. Each category builds on the previous one.
56% Click increase in 28 days from technical fixes only — no new content, no new backlinks
500+ Audits delivered — the same technical issues appear in over 60% of sites audited
30 Specific checks in the foundation checklist — organized in priority order
First Technical foundation before content, every time — this is the rule that changes results
Why Technical SEO Comes Before Everything Else
I want to address a belief I encounter regularly in audit conversations: the idea that content is the primary driver of SEO and technical factors are secondary fine-tuning.
The data does not support this. The clearest demonstration from our own client work: a 56 percent increase in organic clicks in 28 days from technical fixes only. No new content published. No new backlinks built. Just three technical errors corrected — canonical issues, missing H1 headings on 14 service pages, and oversized images causing mobile LCP above 8 seconds.
The content already existed. The potential was already there. The technical errors were suppressing what the content was capable of. Fixing them released that potential.
This is what happens consistently. A site with good content and poor technical health underperforms relative to what its content should achieve. A site with average content and excellent technical health outperforms expectations. And a site with good content and excellent technical health compounds over time in a way that neither alone can produce.
The 30-Point Technical SEO Foundation Checklist
Work through these in category order. Categories 1 and 2 must be complete before any content work. Categories 3 through 6 can run in parallel once 1 and 2 are done.
CATEGORY 1 — CRAWL AND INDEXATION (DO THESE FIRST)
1. robots.txt verified — Confirm Googlebot, Bingbot, GPTBot, ClaudeBot, and PerplexityBot are all allowed. Navigate to yourdomain.com/robots.txt and verify no unintended Disallow rules exist. A single incorrect Disallow line can block entire site sections from indexing.
2. XML sitemap submitted to Google Search Console — Every indexable page listed, no 301 redirects included, no noindex pages included, no 404 pages included. Submit via GSC > Sitemaps. Verify GSC shows it as successfully parsed.
3. llms.txt file live at domain root — Navigate to yourdomain.com/llms.txt. If 404, this file is missing. Create and upload — it directs AI crawlers to your most relevant content and affects ChatGPT, Perplexity, and Claude citation eligibility.
4. No accidental noindex tags on live pages — Search your page source for ‘noindex’ on homepage, key service pages, and blog articles. Staging environments often carry noindex settings to live sites. This is one of the most common and most damaging indexation errors.
5. GSC Coverage report checked for Excluded pages — Any page in the Excluded section of GSC Coverage that should be indexed is a problem. Check specifically: Crawled but currently not indexed (thin content signal), Discovered but currently not indexed (crawl budget issue), Duplicate without user-selected canonical (canonical error).
CATEGORY 2 — CANONICAL TAGS AND URL STRUCTURE (FIX BEFORE PUBLISHING CONTENT)
6. Self-referencing canonical tag on every indexable page — Every page should contain a canonical tag pointing to its own preferred URL. Without this, Google must decide which URL version to treat as canonical — and it does not always choose correctly. Missing canonicals cause duplicate content issues at scale.
7. Single consistent URL format across entire site — Choose one: www or non-www, trailing slash or no trailing slash, HTTP or HTTPS. Every other version should 301 redirect to the canonical format. Mixed URL formats split authority across multiple versions of the same page.
8. No canonical tag errors in Screaming Frog — Run Screaming Frog crawl, go to Canonicals tab. Identify any pages with missing canonicals, canonicals pointing to 404s, canonicals pointing to redirects, or pages with multiple conflicting canonical tags. Each of these is an authority leak.
9. URL structure clean and keyword-relevant — URLs should be: lowercase, hyphenated (not underscored), descriptive of the page content, free of unnecessary parameters. /local-seo-hvac-companies/ is good. /page?id=342&cat=services is not.
10. No pagination issues on blog or archive pages — Blog archive pages often create canonicalization problems. Page 2 of a blog (/blog/page/2/) should either have its own canonical or use rel=prev/next pagination. Paginated pages canonicalizing to page 1 is a common error that hides content from Google.
CATEGORY 3 — SCHEMA MARKUP AND STRUCTURED DATA (IMPLEMENT BEFORE LAUNCH)
11. Organization or LocalBusiness schema on homepage — This is the most important schema type for entity clarity. It explicitly defines your business name, address, phone, URL, logo, service area, and — critically — sameAs links to your GBP, LinkedIn, and other authoritative external profiles. Without it, Google infers your entity from context rather than explicit data.
12. Service schema on every service page — Each service you offer deserves its own Service schema specifying the service name, description, area served, and provider. This is required for service-related rich results and significantly improves AI citation accuracy for service-specific queries.
13. FAQPage schema on all FAQ sections — Every page with Q&A content needs FAQPage schema. This is the primary structured data type for featured snippets and AI citation eligibility. Validate with Google Rich Results Test. Schema questions must exactly match visible page text.
14. Article or BlogPosting schema on all blog content — Every blog post and article needs Article schema with datePublished, dateModified, author (linking to a Person schema), and headline. This feeds E-E-A-T signals and is required for eligibility in Top Stories and Article rich results.
15. Author (Person) schema on all bylined content — Person schema with name, jobTitle, url (linking to an About or author profile page), and sameAs links to LinkedIn. This is the schema that connects author identity to content and contributes directly to E-E-A-T evaluation.
16. BreadcrumbList schema on all interior pages — Breadcrumbs appear in Google search results and help Google understand your site hierarchy. They also improve user navigation and reduce bounce rates by helping visitors understand where they are in the site structure.
17. All schema validated in Google Rich Results Test — Navigate to search.google.com/test/rich-results and test every schema type on your key pages. Any error or warning needs to be resolved. Invalid schema does not produce rich results and can be flagged as misleading structured data if it contradicts visible content.
CATEGORY 4 — CORE WEB VITALS AND PAGE SPEED (CRITICAL POST-MARCH 2026)
18. Mobile LCP under 2.5 seconds on all key pages — Run PageSpeed Insights on mobile for homepage, top service pages, and top blog posts. LCP above 2.5 seconds is classified as Needs Improvement. Above 4 seconds is Poor. Since the March 2026 composite CWV update, poor LCP now suppresses your composite CWV score across all three metrics.
19. All images in WebP format and under 100KB — Uncompressed images are the most common cause of poor mobile LCP. Convert all images to WebP format and compress each to under 100KB before upload. This single action typically improves mobile LCP by 2 to 4 seconds on most business websites.
20. INP under 200ms on all pages — Interaction to Next Paint measures how fast a page responds to user interaction. Poor INP is typically caused by heavy JavaScript, large DOM size, or blocking third-party scripts. Defer non-critical JavaScript and audit all third-party plugins for performance impact.
21. CLS under 0.1 on all pages — Cumulative Layout Shift measures visual stability. Poor CLS is typically caused by images without explicit dimensions, late-loading fonts, or dynamically injected content that pushes page elements. Add explicit width and height attributes to all images and iframes.
22. fetchpriority=’high’ on hero image — The largest image above the fold should have fetchpriority=’high’ in its HTML tag. This tells the browser to load it before other images, directly improving LCP on most pages.
CATEGORY 5 — ON-PAGE SIGNALS (CONTENT FOUNDATION)
23. Unique H1 on every page — Every page should have exactly one H1 heading that describes the page’s primary topic and includes the target keyword. Missing H1s are still one of the most common technical issues in audit data. Pages without H1s rank lower than equivalent pages with them.
24. Unique meta title and description on every page — No duplicate meta titles or descriptions across the site. Each should accurately describe the page content, include the primary keyword naturally, and be within character limits (title: under 60 characters, description: under 160 characters).
25. Descriptive alt text on all images — Every image should have alt text that describes what the image shows. Alt text serves accessibility requirements, contributes to image search visibility, and helps Google understand page content when images contain relevant context.
26. Internal linking structure follows hub-and-spoke model — Each primary service page (hub) should receive internal links from multiple supporting pages (spokes). Every new article or blog post should link to at least one service page. Orphan pages — pages with no internal links pointing to them — receive no authority from the rest of the site.
CATEGORY 6 — ADVANCED SIGNALS (BUILD ON TOP OF CATEGORIES 1-5)
27. 301 redirects for all changed or deleted URLs — Every URL that has been changed or removed should have a direct 301 redirect to the most relevant current page. No redirect chains longer than 2 hops. Check Screaming Frog Response Codes for any chains or redirect loops.
28. Crawl budget health for large sites — For sites with over 500 pages, run a crawl budget analysis. Check GSC Crawl Stats report for crawl errors and crawl rate. Ensure Googlebot is not wasting crawl budget on paginated archive pages, URL parameters, or session IDs that produce duplicate content.
29. Open Graph and Twitter Card meta tags on all pages — Social sharing metadata ensures your pages display correctly when shared on LinkedIn, Twitter/X, and Facebook. Missing OG tags result in poor visual display when pages are shared, reducing click-through rates from social traffic.
30. Mobile-first verified — all content accessible on mobile — Google indexes the mobile version of your site. Any content that is only visible on desktop — in hidden tabs, desktop-only accordions, or elements hidden from mobile via CSS — is not indexed. Verify all key content is accessible in Google’s mobile rendering.
Result: These 30 checks, completed before publishing any new content, produce faster ranking results from every piece of content subsequently published. The foundation is not a one-time project — audit it quarterly and after any significant site change.
If the March Update Hit You — The 5 Immediate Actions
The March core update finished rolling out on April 8. If your rankings dropped during the rollout window and have not recovered, here is the priority sequence. Do these in order — not simultaneously.
1. Run PageSpeed Insights on mobile for your top five pages. Check the three CWV metrics. If any are Poor, that is your first fix. Since the March composite CWV change, a poor score on any single metric is now suppressing all three. This is often the fastest win available.
2. Pull Google Search Console Performance data. Compare March 1-23 vs April 9-30. Identify which specific pages dropped and on which dates. This tells you whether the spam update (March 24-25 drops) or the core update (gradual drops March 27 – April 8) was responsible.
3. For pages that dropped, check content quality. Is each page the most comprehensive, expert, and useful resource available on its topic? Pages that dropped in a core update are almost always pages where a competitor now offers more depth, more specificity, or more verifiable expertise.
4. Check author signals on your content. If blog articles and guides have no author attribution, no Author schema, and no verifiable credentials associated with the content, add them. E-E-A-T signals are evaluated at the page level but affect domain-level trust signals over time.
5. Do not make large structural changes while waiting for recovery. Making multiple significant changes to a site during a post-update stabilization period extends the processing timeline. Make targeted improvements to specific underperforming pages. Submit those pages via GSC URL Inspection. Then wait.
Warning: Core update recovery is typically validated at the next core update — not immediately after making improvements. The May 2026 core update is the first major opportunity for sites that were penalized in March to show recovery. Changes made in April will be evaluated then.
Free SEO Audit — full technical health check.
What Makes a Site Update-Proof — The Pattern From 500+ Audits
After 500-plus audits, the sites that hold through every core update share a specific set of characteristics. None of them are sophisticated. All of them are intentional.
| Characteristic | Update-Proof Site | Site at Risk |
| Technical foundation | 30-point checklist clean, audited quarterly | Technical issues present and unaddressed for months |
| Content authorship | Named, credentialed authors on all key content | Anonymous content with no verifiable expertise |
| Content depth | Most comprehensive resource on each topic covered | Surface-level overviews targeting keyword density |
| Indexation hygiene | Only quality pages in the index | Thin, outdated, and duplicate pages indexed alongside good content |
| Core Web Vitals | All three metrics at Good on mobile | One or more metrics at Poor or Needs Improvement |
| Schema implementation | All relevant types present and validated | Missing or invalid schema across most pages |
| Content publishing rate | Consistent quality publishing — fewer, better pieces | High-volume publishing with inconsistent quality |
| AI crawler access | llms.txt present, all AI crawlers allowed | No llms.txt, AI crawlers blocked or unaddressed |
None of these are things that require a large budget or a large team. They require intentional decisions made consistently over time. The businesses that stay stable through algorithm changes are the ones that built correctly from the start and kept maintaining what they built.
What Is Coming in May — A Preview
May 2026 brought the most significant news in search in years: Google I/O 2026, where Google announced AI Mode as the new default search experience. This is the biggest change to how Google presents search results in 25 years.
Alongside Google I/O, the May core update ran from May 21 to June 2 — reinforcing the same people-first content signals from March but with specific implications for how AI Mode content is evaluated.
The May newsletter covers both: what AI Mode actually is and what it means for your business, and what the May core update targeted that the March update did not. If you are not subscribed to the newsletter, this is the issue you most need to receive.
Subscribe to the Dexora Digital Newsletter
Your April 2026 Action List
Action 1: Run the 30-point checklist — Work through all six categories. Start with Category 1 — Crawl and Indexation. Nothing else is worth fixing if Google cannot access your pages.
Action 2: Check PageSpeed Insights mobile for top 5 pages — Identify your weakest CWV metric. Fix it before publishing any new content this month.
Action 3: Verify llms.txt exists at domain root — yourdomain.com/llms.txt — 404 means it is missing. Create it. This is a 30-minute task that affects AI citation eligibility.
Action 4: Run Screaming Frog on your site — Export the full crawl. Check: missing H1s, missing meta descriptions, pages returning errors, canonical tag issues, redirect chains. Fix the highest-volume issues first.
Action 5: Check GSC Coverage report — Identify pages in Excluded that should be indexed. Pay specific attention to Crawled but currently not indexed — this often indicates thin content that Google visited but decided not to rank.
Action 6: Add Author schema to your top 10 articles — If blog posts and guides have no Author schema, add it. Link the author name to a Person schema with verifiable credentials.
Action 7: Identify and noindex 5 of your thinnest pages — Every site has pages that should not be in Google’s index — old stub posts, placeholder pages, duplicate service area pages. Removing them from the index is a quality signal for the pages that remain.
Action 8: Set a quarterly technical audit reminder — Technical issues accumulate over time — plugins added, pages created, URLs changed, schema broken. A quarterly 30-point checklist review catches issues before they suppress rankings.
Key insight: May newsletter covers Google I/O 2026 and the AI Mode announcement — the biggest search product change in 25 years. It also covers the May core update. Make sure you are subscribed so you receive it the week it publishes.
Frequently Asked Questions — Technical SEO Foundation
Q: What is the most important technical SEO fix to make in April 2026?
A: Following the March 2026 composite Core Web Vitals update, the highest-priority technical fix is identifying and resolving any CWV metric scoring Poor on mobile. Run Google PageSpeed Insights on your homepage and top service pages using the mobile test. If LCP is above 4 seconds, INP is above 500ms, or CLS is above 0.25, that metric is Poor and is now suppressing your composite CWV score. Image compression (converting to WebP and compressing under 100KB) is the fastest fix for most sites with poor LCP, as uncompressed images are the most common cause.
Q: What is a canonical tag and why does it matter for SEO?
A: A canonical tag is a line of code in a page’s HTML head section that tells Google which URL is the preferred version of a page. Without canonical tags, Google may discover multiple URL versions of the same page — http vs https, www vs non-www, trailing slash vs no trailing slash, or URL parameters — and split authority across all of them rather than concentrating it on the preferred version. Self-referencing canonical tags (each page canonicalizing to its own URL) are the minimum requirement. Every indexable page on your site should have one.
Q: How often should I run a technical SEO audit?
A: A full technical SEO audit should be run quarterly, and also after any significant site change — a redesign, a CMS migration, a major content addition, or a hosting change. Technical issues accumulate incrementally. A plugin added in February may conflict with another plugin and break schema markup in March. A URL changed by a content editor may create an unintended orphan page. Quarterly audits catch these issues before they compound. Between full audits, set up Google Search Console alerts for coverage errors and watch the GSC Coverage report weekly for new Excluded pages.
Q: What is crawl budget and does it matter for small business websites?
A: Crawl budget is the number of pages Googlebot will crawl on a given site in a given period. For small business websites with fewer than 200 pages, crawl budget is rarely a concern — Google will crawl the entire site regularly. Crawl budget becomes relevant for sites with hundreds or thousands of pages, particularly when significant portions of those pages are low-value: paginated archive pages, URL parameter variations, duplicate service area pages, or outdated content. For large sites, improving crawl budget efficiency means ensuring Googlebot spends its crawl allocation on quality pages rather than thin or duplicate ones.
Q: Does schema markup directly improve Google rankings?
A: Schema markup does not directly improve standard organic rankings. What it does is make pages eligible for rich results — featured snippets, FAQ dropdowns, star ratings, product information — which increase the visual prominence of search results and improve click-through rates at the same ranking position. Schema also helps Google and AI systems explicitly understand page content and entity relationships, which contributes indirectly to topical authority evaluation. The indirect effects on rankings are real and measurable over time, even though schema is not a direct ranking factor.
Q: What is the hub-and-spoke internal linking model?
A: The hub-and-spoke model is an internal linking architecture where primary service or topic pages (hubs) receive internal links from multiple supporting content pages (spokes). For example, an HVAC company’s AC Repair service page is the hub. Blog posts about ‘why is my AC not cooling,’ ‘how often should I service my AC,’ and ‘AC vs heat pump comparison’ are the spokes — each links back to the AC Repair hub page. This distributes authority from the high-traffic informational content to the commercial service pages, which is where conversion happens. Without this structure, informational pages and service pages exist as disconnected silos with no authority flow between them.
Q: How do I find and fix orphan pages on my website?
A: Orphan pages are pages with no internal links pointing to them from other pages on the site. Google discovers pages primarily by following links — an orphan page may never be crawled, and even if crawled, receives no authority from the rest of the site. To find orphan pages: run Screaming Frog on your site and export the full URL list. Then cross-reference against your XML sitemap and your GSC Coverage report. Any URL that appears in GSC or your sitemap but has zero internal links pointing to it in the Screaming Frog inlinks data is an orphan. Fix by adding contextually relevant internal links from existing pages to the orphan.
Q: What is the difference between a 301 and 302 redirect for SEO?
A: A 301 redirect is permanent — it tells Google the page has moved to the new URL indefinitely and transfers link equity from the old URL to the new destination. A 302 redirect is temporary — it tells Google the page has moved temporarily, and Google may continue to index the original URL and withhold link equity transfer. For SEO purposes, almost all redirects should be 301. The only case for a 302 is when a page is genuinely temporarily unavailable — a product page out of stock that will return, or a page under maintenance. Using 302 redirects for permanent URL changes is a common technical error that prevents link equity transfer.
Q: Should I remove old blog posts that are not generating traffic?
A: Evaluate before removing. An old blog post that is not generating traffic might be in one of three situations: thin content that Google visited and decided not to rank (noindex or improve it), a topic with genuine search demand that is poorly optimized (improve it — it has potential), or a topic with no meaningful search demand that is not harmful to keep (leave it, low priority). Removing a page that has external backlinks pointing to it destroys that link equity unless you implement a 301 redirect to a relevant replacement. A noindex tag is preferable to deletion for pages that might have external links, as it removes the page from Google’s index while preserving the page’s ability to pass link equity through any backlinks it has earned.
Q: How does Core Web Vitals affect local businesses specifically?
A: For local service businesses, Core Web Vitals matters more than for most other business types because 70 to 80 percent of local search traffic arrives on mobile devices, and mobile is where CWV scores are lowest and where the impact of poor scores is highest. A local plumbing company with a mobile LCP of 8 seconds is losing a significant percentage of potential clients who search on their phone during an emergency and click away before the page loads. Since the March 2026 composite CWV update, a poor mobile LCP also suppresses INP and CLS scores in the composite evaluation. For local businesses, mobile CWV is not an optional optimization — it directly affects both rankings and conversion rates.
ABOUT THE AUTHOR
Taqweem Ahmad
Founder, Dexora Digital | Technical SEO Specialist | 7+ Years | 500+ Audits
Taqweem Ahmad founded Dexora Digital, a full-stack SEO and AI Search agency in Oulu, Finland. Over 7 years and 500+ audits, the consistent finding is that technical foundation work produces faster results from every other investment — content, links, and ads all perform better on a technically correct site.
[email protected] | dexoradigital.com | dexoradigital.com/newsletter/
