WordPress Technical SEO – URL Structure, Sitemap, Robots.txt, Structured Data, and Indexing Optimization

Published: March 20, 2026 · Author: Marcin Szewczyk-Wilgan

Technical SEO is the foundation of search engine visibility. You can have the best content in the world, but if Google cannot properly crawl, index, and understand your site – that content will not appear in results. WordPress provides solid SEO fundamentals, but its default configuration is not optimized. URL structure, XML sitemap, robots.txt, Schema.org structured data, canonical tags, hreflang, Core Web Vitals – these elements determine whether Googlebot effectively crawls your site and how it is presented in results. This article covers the key elements of WordPress technical SEO and specific steps for proper configuration.

URL Structure – Readable, Logical, Permanent

URL structure is the first technical SEO element to configure – and one of the most important. Clean URLs help both users and search engines understand page content.

PermalinksWordPress defaults to ?p=123 URL format. Change to “Post name” (/%postname%/) in Settings → Permalinks. This gives readable, descriptive URLs: /wordpress-optimization/ instead of /?p=47. This change should be made immediately after WordPress installation – later changes require 301 redirects.
Hierarchy and logicURL structure should mirror the site structure. For larger sites, consider hierarchy: /services/wordpress-optimization/, /know-how/core-web-vitals/. Avoid URLs deeper than 3 levels. Categories in URLs – only if they add informational value.
Keywords in URLsURLs should contain the main keyword – short and specific. /wordpress-optimization/ is better than /how-to-optimize-your-wordpress-site-to-make-it-faster/. Avoid special characters, stop words, and unnecessary words.
URL permanenceChanging a published page’s URL means losing all links pointing to the old address. If you must change a URL – always configure a 301 redirect from old to new. Never leave a 404 where there was content with backlinks.

XML Sitemap – A Site Map for Search Engines

An XML sitemap is a file informing search engines about all site pages that should be indexed. WordPress generates a native sitemap since version 5.5, but its capabilities are limited.

Native WordPress sitemapAvailable at /wp-sitemap.xml. Contains posts, pages, categories, tags, and custom post types. Basic functionality – no control over what is in the sitemap, no priorities, no modification dates. Sufficient for simple sites.
SEO plugin sitemapSEO plugins (Yoast, Rank Math) generate advanced sitemaps: with last modification date, ability to exclude content types, separate sitemaps for posts, pages, categories, images. Full control – this is the recommended solution.
Submitting to GoogleSubmit the sitemap in Google Search Console (Sitemaps → Add a new sitemap). Monitor status: how many pages submitted, how many indexed, any errors. A sitemap does not guarantee indexing – but it informs Google about the site structure.
Hreflang in sitemapFor multilingual sites – the sitemap should contain xhtml:link tags with hreflang attributes, pointing to language equivalents of each page. This is the most reliable way to communicate the site’s language structure to search engines.

Robots.txt – Crawl Control

Robots.txt is a file in the site’s root directory that tells search engine bots which parts of the site they can crawl and which to avoid. It does not block indexing – it blocks crawling.

Default WordPress robots.txtWordPress generates a virtual robots.txt with basic rules. Blocks access to /wp-admin/ (but allows /wp-admin/admin-ajax.php, needed by many plugins). Points to the sitemap location. For most sites, this is a sufficient starting point.
What to blockPages with no SEO value that waste crawl budget: /wp-admin/, internal search results pages (?s=), filter pages with parameters, low-value tag pagination pages, author pages (if single author). Do not block CSS and JS – Google needs them to render the page.
Robots.txt vs noindexRobots.txt blocks crawling – but if a page has external links, Google may index it despite the robots.txt block (without crawling the content). To block indexing, use the noindex meta tag, not robots.txt. This is a common mistake leading to “indexed but blocked” pages.

Structured Data – Schema.org

Structured data are JSON-LD markup in the page code that help search engines understand the type and content of a page. They enable rich snippets in Google results – FAQ, review stars, breadcrumbs, events, products.

Article

Articles and posts

Article schema for blog posts and articles. Contains: headline, author, publish date, modification date, description. Helps Google display the publication date in search results and classify the content as editorial.

FAQPage

FAQ sections

FAQPage schema for frequently asked questions. Enables FAQ rich snippets directly in search results – expandable questions and answers below the link. Significantly increases click-through rate and SERP real estate.

LocalBusiness

Local businesses

LocalBusiness schema for company sites. Contains: name, address, phone, opening hours, geo coordinates. Enables display in Google Maps and local pack. Essential for companies serving local markets.

Product

WooCommerce products

Product schema for online store products. Contains: name, price, availability, reviews. Enables product rich snippets with price and availability in search results. WooCommerce adds basic Product schema – SEO plugins extend it.

Canonical, Noindex, and Crawl Budget

Crawl budget management is an advanced technical SEO element, particularly important for larger WordPress sites with thousands of URLs.

Canonical tagThe <link rel="canonical"> tag indicates the preferred version of a page when the same content is available at multiple URLs (e.g. with UTM parameters, with and without www, HTTP and HTTPS). WordPress and SEO plugins add canonical automatically – but verify they point to the correct URL.
Meta noindexPages that should not appear in Google: search results pages, low-value tag pages, archive pagination pages, media attachment pages. Set noindex in the SEO plugin – a clean solution that tells Google “do not index this page.”
Crawl budgetGoogle allocates each site a limited crawl budget. If Googlebot wastes time crawling insignificant pages (tags, date archives, filter parameters), less time remains for important content. Crawl budget optimization: noindex on low-value pages, block unnecessary paths in robots.txt, internal linking to key pages.
301 redirectsURL change, page deletion, structure change – always configure a 301 redirect from old to new address. Redirect chains (A→B→C→D) waste crawl budget and slow down the site. Maximum one redirect between old and new URL.

Speed and Core Web Vitals as an SEO Element

Core Web Vitals (LCP, INP, CLS) have been an official Google ranking factor since 2021. Site speed is not just UX – it directly impacts search rankings.

LCP below 2.5sLargest Contentful Paint – the loading time of the main element. Depends on hosting (TTFB), image optimization, cache, and render-blocking resources. Only 44% of WordPress sites on mobile meet LCP requirements.
HTTPS mandatoryGoogle has favored HTTPS sites for years. Chrome marks HTTP pages as “Not Secure.” An SSL certificate is the absolute minimum – without it, Google may lower rankings and display a warning to users.
Mobile-first indexingGoogle indexes and evaluates the mobile version of a site as the primary version. If the mobile version is slow, has less content, or worse navigation than desktop – that version determines search rankings. Responsiveness is not optional – it is a requirement.

Summary

Technical SEO is not a one-time setup – it is an ongoing process. New pages, structural changes, WordPress and plugin updates, Google algorithm changes – all require regular audits and optimization. Technical fundamentals (URL structure, sitemap, robots.txt, structured data, canonical, speed, HTTPS) must be correct before investing in content and link building. Without them – even the best content will not reach its full potential in Google.

At WebOptimo, technical SEO is part of every WordPress deployment – from URL structure and structured data, through sitemap and robots.txt configuration, to Core Web Vitals optimization. If you want a technical SEO audit of your site – contact us or check our WordPress optimization and website development offer.

Frequently Asked Questions About WordPress Technical SEO

Optimization of a site’s infrastructure so search engines can efficiently crawl, index, and understand content. Without it, even the best content will not reach its potential in search results.

WordPress provides a solid foundation, but default configuration is not optimized. URL structure, sitemap, structured data, canonical – all need configuration. With proper setup, WordPress is excellent for SEO.

For most sites – yes. Yoast SEO or Rank Math provide advanced sitemaps, structured data, canonical control, noindex settings, and meta tag editing. The native WordPress sitemap is basic.

JSON-LD markup in page code helping search engines understand page type and content. They enable rich snippets: FAQ, stars, breadcrumbs, products. Schema.org is the standard vocabulary.

Google Search Console (indexing, errors, Core Web Vitals), PageSpeed Insights (performance), Rich Results Test (structured data), Screaming Frog (crawl audit), Ahrefs/Semrush (comprehensive audit).

Let’s Talk About Your Google Visibility

We will audit your technical SEO and implement improvements. No commitments – a concrete proposal after analysis.

Phone

+48 608 271 665

Mon–Fri, 8:00–16:00 CET

E-mail

contact@weboptimo.pl

We respond within 24h

Company

WebOptimo

VAT ID: PL6391758393