Technical SEO is the ranking foundation upon which content and link building can stand. A site with great content but a weak technical foundation captures a fraction of the available traffic. This article breaks the WordPress technical SEO audit into 12 field-tested points, with concrete tools, common traps, and pointers for both DIY audits and professional engagements.
What “technical SEO” means in 2026
Technical SEO is everything beyond content and external links that affects how search engines crawl, index, parse, and present your site. In 2026 the definition extends to optimisation for AI search engines: Perplexity, Bing Chat, Google AI Overviews, ChatGPT browsing. All those systems crawl under the same rules as the traditional Google bot, but they add a layer of context and structure understanding.
Three core dimensions of technical SEO: indexability (can the site be indexed at all), crawlability (can the crawler reach every important URL), parseability (does the HTML structure and schema markup help the bot understand the content). The audit covers all three dimensions in a structured way.
A frequent client misconception: “our content is great, SEO must be fine”. Content is just one of three variables. A site with 200 strong articles but missing schema markup, broken robots.txt blocking crawling, and 40 percent of pages with a noindex tag loses 60 to 80 percent of its potential traffic. The Hanse Studio website audit separates these variables and delivers a concrete fix list per dimension.
Points 1-4: indexability foundation
The first four points of a technical SEO audit cover indexability: does Google even know that your site exists and can it index it.
Point 1: robots.txt. We verify the file is available under /robots.txt, that it does not block crawling of important paths, that it does not include common mistakes like Disallow: / or Disallow: /wp-admin/ (which also blocks admin-ajax.php used by the frontend). A common WordPress trap: the default robots.txt with the Discourage Search Engines flag enabled in Settings – Reading. The first 30 second quick win.
Point 2: sitemap.xml. We verify the sitemap exists (auto-generated by Yoast or RankMath), that it contains every published page and post, that links in the sitemap return 200, that there are no URLs with noindex or canonical pointing to a different page. A sitemap submitted in Google Search Console helps Google discover new content faster, critical for blogs.
Point 3: noindex policy. Pages with thin content (tag archives, pagination, author archives, attachment pages) should carry a noindex tag, so they do not dilute the crawl budget. Common trap: the default Yoast configuration does not set noindex on attachment pages, which leads to hundreds of indexed URLs with one image each. The audit checks that noindex sits on the correct content types.
Point 4: canonical URLs. Every page with duplicate content (for example WooCommerce products with multiple URL variants, pagination, sorted listings) should carry rel=”canonical” pointing to the master version. A missing canonical or a broken canonical (self-referencing with URL parameters) causes Google to index every variant and dilute authority. RankMath and Yoast handle this automatically, but custom themes often break canonical in hero sections or pagination.
A practical observation from Hanse Studio audits: 30 percent of client sites have at least one of these four points misconfigured, which costs them on average 25 percent of potential organic traffic. Each of these four points is a quick win requiring 30 minutes to 2 hours of work, so audit ROI in this dimension often hits 5 to 10x in the first quarter post-implementation.
Points 5-7: structured data (schema.org)
Structured data is JSON-LD markup that tells the bots exactly what your page represents. Without schema markup, Google relies on heuristics (heading hierarchy, content patterns), which works only sometimes. With schema markup Google receives precise information, which unlocks rich results in the SERP (rich snippets, knowledge panels, FAQ accordions, recipe cards).
Point 5: Organization schema. The homepage should carry JSON-LD Organization schema with name, url, logo, contactPoint, sameAs (links to social media). Plus a full address property with PostalAddress (critical for local SEO). Hanse Studio recommends a full Organization markup with 8 to 12 properties, so Google has a complete view of the company.
Point 6: Article/BlogPosting schema on every blog post. Properties: headline, author (with @type Person plus url to author page), datePublished, dateModified, image, publisher (with @type Organization). Additionally wordCount, articleSection, inLanguage for multilingual sites. These are E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness) critical for YMYL niches.
Point 7: Breadcrumb schema plus FAQ schema. Breadcrumb helps Google understand the navigation structure and can render a breadcrumb in the SERP instead of the URL. FAQ schema on FAQ blocks (like the one at the end of this article) unlocks rich results in the SERP with expandable Q&A. WooCommerce adds Product schema by default with price, availability, aggregateRating.
Validation: Google Rich Results Test (rich-results-test) plus the schema.org validator. Every page with schema markup should pass both tests. WordPress LiteSpeed Cache trap: JS minification can eat inline JSON-LD scripts, so the audit checks that structured data is delivered to the crawler unmodified.
A real incident from our own studio site: LiteSpeed Cache JS minification was eating the JSON-LD Organization schema, which only the post-deploy Rich Results Test surfaced. The fix required adding data-no-optimize=”1″ and data-no-minify=”1″ attributes on the inline script tags plus using wp_json_encode instead of manual JSON strings. Lesson: always validate schema after enabling cache optimisation plugins, JS minify can silently break structured data.
Additionally for e-commerce: Product schema with aggregateRating and price needs a manual review after every pricing change. The WooCommerce default Product schema (via the RankMath WooCommerce add-on) is fine, but custom price ranges (for example “from 1500 PLN”) require a custom JSON-LD override. The Hanse Studio audit for stores covers a sample of 20 products with various prices and validation in Rich Results Test.
Points 8-10: multilingual and hreflang
Multilingual sites (Hanse Studio domains default to 5 languages: PL, EN, DE, FR, CS) introduce an extra layer of complexity in technical SEO. Three audit points are specific here.
Point 8: hreflang tags. Every page with a translation in another language should carry rel=”alternate” hreflang=”lang-CODE” link tags pointing to all other language versions plus a self-reference. Plus an x-default href for the default fallback. A common Polylang Free trap: it does not generate hreflang automatically, requiring a custom hook in functions.php or a plugin extension.
Point 9: separate sitemap per language or a combined sitemap with hreflang. Google recommends a sitemap with hreflang for smaller sites (up to 1000 URLs), separate sitemaps per language for larger ones. Polylang Pro handles this automatically, Polylang Free requires manual setup in Yoast or RankMath.
Point 10: per-lang meta tags. Title, description, OG image should be per-language, not just per-page. Polylang Free trap: it does not support per-lang meta tags without custom code. Hanse Studio uses a custom i18n.php pattern with a gettext filter that translates title and meta description at the wp_head level. The audit checks that meta tags actually differ between PL and EN versions.
A frequent finding in Hanse Studio audits for multilingual sites: the title tag is in Polish for every language version, even though the content is translated. The English version then shows up in Google search with a Polish title, which dramatically drops CTR (English speakers do not click Polish titles). Fix needs 2 to 3 hours of custom code in i18n.php plus testing in Rich Results Test per language.
Additionally: OG image (og:image meta tag) should be per-language if the image contains text. A PL page with an OG image “Audyt strony WWW” in Polish, the EN version should carry a separate OG image with “Website audit” in English. Without it, social shares from the EN page look like Polish content, which damages brand perception on DACH LinkedIn.
Points 11-12: mobile and Pagespeed signals
The last two points join mobile UX with Pagespeed signals, which has been one integrated signal for Google since 2021.
Point 11: mobile usability. The audit verifies that the viewport meta tag is set correctly (width=device-width, initial-scale=1), that touch targets are at least 48 pixels (Apple HIG and Material Design guidance), that text is readable without zoom (min 16px on mobile), that there is no horizontal scrolling beyond the viewport. The Google Search Console “Mobile Usability” report (replaced by the Page Experience report in 2023) used to flag these issues.
A frequent finding: a page with a desktop hero image in the viewport background generates horizontal scroll on mobile (overflow-x hidden is missing). A second frequent issue: floating action buttons (a WhatsApp widget, scroll-to-top arrow) overlap the main CTA, frustrating the user’s thumb. The audit simulates touch interaction in Chrome DevTools mobile emulator at multiple viewport sizes (360px, 414px, 768px).
Point 12: Core Web Vitals as a ranking factor. LCP, INP, CLS as in our dedicated article. Point 12 does not repeat that analysis, it only verifies that CrUX field data is in the “good” range for all three metrics. If not, the finding is flagged for a separate performance audit.
All 12 points together form the audit checklist that Hanse Studio walks through systematically in 6 to 8 hours of work for an average corporate site. The deliverable is a PDF report with findings per point, P0/P1/P2/P3 prioritisation, a quick wins list and larger projects for BACKLOG. The client leaves the audit with a clear 90 day technical SEO improvement plan.
Tools: GSC vs Ahrefs vs Screaming Frog vs Sitebulb
A technical SEO audit uses 3 to 4 tools in sequence. Every tool has its focus area.
Google Search Console is free and mandatory. It shows real index status (which pages Google has in the index and which not), coverage issues (404, redirect chains, soft 404), Core Web Vitals field data, Mobile Usability, Performance (CTR, impressions, position per keyword). Every production site must have GSC wired in before the audit.
Submitting sitemap.xml in GSC is the first post-launch step. Without it, Google discovers the site through external links, which for a small business can take 2 to 4 weeks. With a submitted sitemap, the typical crawl picks up the first 10 to 20 pages within 48 hours. Plus regular monitoring of the “Pages” tab shows which pages were dropped from the index (typically due to noindex tag, duplicate content, or thin content signal).
Ahrefs Site Audit ($99 to 499 per month) is a paid tool for competitive analysis. It shows your issues plus a comparison against 2 to 3 competitors, broken links discovery, internal linking opportunities, content gaps. For a freelancer or a small agency Hanse Studio recommends the $99 plan (1 site, monthly audit) with shared access for the client.
Screaming Frog SEO Spider is a desktop crawler (259 EUR per year, or free up to 500 URLs). It gives a deep technical view: every URL with status code, h1, meta, schema, canonical, hreflang, internal and external links. Custom extraction with XPath enables advanced audits (find all pages without H1, all images without alt). Hanse Studio standard tool for Tier 1 audits.
Sitebulb (35 GBP per month) is the Screaming Frog alternative with better visualisation and pretty reports for clients. It auto-prioritises issues, generates an executive summary, exports to PDF. Hanse Studio uses Sitebulb for Tier 2 and Tier 3 audits, where the client receives the report as a deliverable.
As a complement: Lighthouse in Chrome DevTools for the SEO audit category (auto-detection of meta tags, robots.txt, sitemap, hreflang, image alt). Plus the custom Hanse Studio audit-clientsite skill based on Chrome DevTools MCP, which combines all the above tools into one automated pipeline with a markdown report output.
AI search optimisation in 2026
AI search engines (Perplexity, Bing Chat, Google AI Overviews, ChatGPT browsing) crawl sites with the same bots as traditional search engines, but they interpret content differently. AI search optimisation is an extension of technical SEO, not a separate discipline.
Three bonus signals for AI search: FAQ blocks with explicit Q&A structure (AI often cites FAQs in direct answers), listicle structure with numbered lists (AI cites list points in step-by-step responses), expert authorship with author bio and Schema Person (an E-E-A-T signal critical for YMYL).
An additional element: a site with a consistent brand voice and demonstrated expertise (case studies with numbers, methodology articles with step-by-step process) is cited by AI more often than a site with generic marketing copy. AI search is not a replacement for SEO; it is an additional layer, where content quality weighs more than keyword density.
Hanse Studio recommends the stack: WordPress plus Astra Pro plus RankMath plus a custom child theme with schema markup embedded in every Gutenberg block template. Plus a content strategy with Q&A focus and case study driven articles. This stack supports 11 of 12 audit points out-of-the-box, point 10 (per-lang meta tags) requires custom code.
A practical list of AI search wins to roll out in one week: add an FAQ block at the end of every blog post (5 to 7 Q&A pairs), add an author bio with Schema Person markup on every post, add a methodology section in service pages (what our process looks like step by step), add case studies with concrete numbers (before and after, ROI, time to deploy). These four interventions typically deliver a 20 to 30 percent uplift in AI citations in Perplexity and Bing Chat in 60 days.
FAQ
How often should I run a technical SEO audit?
Quarterly for actively developed sites, or after a major site change (theme migration, new plugin, URL restructuring). Monthly for e-commerce with 100+ products. For smaller corporate sites with minimal changes, an annual audit suffices.
Yoast vs RankMath for schema?
The RankMath free plan offers more schema types out-of-the-box (Article, FAQ, HowTo, Recipe, Product, Local Business). Yoast requires Premium for most schema types. The RankMath UX is denser (more options), Yoast is simpler. Hanse Studio recommends RankMath for most clients, Yoast for clients who already have it and do not want to migrate.
Will AI search replace traditional SEO?
It will not replace, it will add a layer. Traditional SEO (a search results page with 10 blue links) is losing share to AI Overviews and direct answers. But in 2026, still 60 to 70 percent of search queries end with a click on an organic result. Strategy: optimise for both scenarios, AI cites pages with strong technical SEO and strong content.
Can I run a technical SEO audit myself?
6 of 12 points yes (GSC analysis, PSI run, robots.txt review, sitemap submit, manual meta tag checks, basic schema validation). The other 6 require tools (Screaming Frog, Ahrefs) plus expertise (interpretation of findings, prioritisation). A small DIY audit in 4 hours versus a professional audit in 8 to 16 hours produces different depth.
If you want a full WordPress technical SEO audit for your site, drop us a line with the page URL. Tier 2 audit (1500 PLN, 8h of work) covers all 12 points plus an additional analysis with Impact x Effort prioritisation. Standard turnaround 5 to 7 business days from a signed contract to a delivered PDF report with concrete implementation steps.