How to Make Your WordPress Site Accessible: A WCAG Compliance Guide
How to Make Your WordPress Site Accessible: A WCAG Compliance Guide | Simple Automation Solutions Home › Guides › WordPress Development WordPress Development How to Make Your WordPress Site Accessible: A WCAG Compliance Guide Over 1 billion people have a disability that affects how they use the web. Here is how to make your WordPress site accessible to everyone — and why it matters for SEO and legal compliance. SAS Simple Automation Solutions ·2026-03-21 ·⏱ 10 min read 1B+ people globally have a disability WCAG 2.1 AA is the legal standard in most countries 4.5:1 minimum contrast ratio for normal text 30% of issues caught by automated tools — manual testing is essential In this guide Why accessibility matters WCAG guidelines explained Choose an accessible theme Fix common issues Accessibility plugins Test your accessibility Frequently asked questions Web accessibility means building websites that can be used by everyone — including people with visual, auditory, motor, or cognitive disabilities. Beyond being the right thing to do, accessibility is increasingly a legal requirement in many countries and a confirmed ranking signal for Google. Here is how to make your WordPress site accessible. Why WordPress accessibility matters Over 1 billion people globally have some form of disability — that is a significant portion of any target audience Legal requirements — the ADA (USA), AODA (Canada), and EN 301 549 (EU) require public-facing websites to meet accessibility standards SEO benefit — many accessibility improvements (alt text, heading structure, descriptive links) also improve how Google understands your content Better usability for everyone — captions help people in noisy environments; clear navigation helps users with slow connections or older devices WCAG guidelines — what they are The Web Content Accessibility Guidelines (WCAG) are the international standard for web accessibility, published by the W3C. WCAG 2.1 Level AA is the benchmark referenced by most legal frameworks. WCAG principle What it means WordPress example Perceivable Content must be perceivable by all users Images have alt text; videos have captions Operable UI must be operable by all input methods Site navigable by keyboard alone; no keyboard traps Understandable Content and UI must be understandable Clear headings; consistent navigation; readable font sizes Robust Content must work with assistive technologies Semantic HTML; proper ARIA labels; valid markup Step 1 — Choose an accessible WordPress theme Accessibility starts with your theme. A poorly coded theme can make compliance nearly impossible to achieve through plugins or content alone. Look for themes that advertise WCAG 2.1 AA compliance: WCAG Compliant Astra Built with accessibility in mind. Passes automated accessibility checks out of the box. Compatible with all major accessibility plugins. WCAG Compliant Kadence Strong accessibility defaults including focus states, skip navigation links, and semantic HTML structure. WCAG Compliant GeneratePress Lightweight with excellent keyboard navigation and screen reader compatibility. One of the most accessibility-friendly WordPress themes. Dedicated Accessibility Ready themes WordPress.org’s accessibility-ready tag filters the repository to themes reviewed for basic accessibility compliance. Step 2 — Fix the most common accessibility issues Image alt text Every meaningful image must have descriptive alt text that conveys its content to screen reader users. Decorative images (backgrounds, spacers) should have empty alt attributes (alt=””) so screen readers skip them. In WordPress, add alt text in the Media Library or in the image block’s Alt Text field Describe what the image shows, not what it is (‘A bar chart showing 40% growth in Q3’ not ‘Chart’) Product images: describe the product as a customer would want to know (‘Red leather Oxford shoe, size 10’) Do not start alt text with ‘Image of’ or ‘Photo of’ — screen readers already announce it as an image Heading structure Headings create a navigable outline of your page for screen reader users. The correct hierarchy is: one H1 per page (the page title), H2s for major sections, H3s for subsections. Never skip heading levels (H1 to H3 without H2). Colour contrast Text must have sufficient contrast against its background. WCAG 2.1 AA requires a contrast ratio of 4.5:1 for normal text and 3:1 for large text. Test your theme’s text/background combinations using the WebAIM Contrast Checker (webaim.org/resources/contrastchecker/). Keyboard navigation All functionality must be operable via keyboard alone — no mouse required. Test by pressing Tab to move through your site and Enter to activate links and buttons. Every interactive element must be reachable and visibly focused. Step 3 — Accessibility plugins for WordPress Audit WP Accessibility Adds skip navigation links, fixes missing form labels, and provides multiple accessibility improvements to WordPress themes. Free. Compliance Helper Accessibility Checker Scans your WordPress content for accessibility errors and provides plain-language guidance on fixing each issue. Free core plugin. Overlay (with caveats) UserWay Adds an accessibility widget that lets users adjust font size, contrast, and spacing. Note: overlays are controversial — they do not replace proper accessibility implementation but can assist some users. ⚡ Accessibility overlays are not a compliance solution Automated accessibility overlays (like UserWay or accessiBe) have been publicly criticised by disability advocates as inadequate for compliance. They can help some users but do not fix underlying code issues. Proper accessibility requires fixing the source HTML, CSS, and content — not adding a widget on top. Step 4 — Test your accessibility 1 Run an automated scan Install the Accessibility Checker plugin or use the WAVE tool (wave.webaim.org). Automated tools catch approximately 30–40% of WCAG issues — they are a starting point, not a comprehensive audit. 2 Test with keyboard only Put your mouse aside. Navigate your entire site using Tab, Shift+Tab, Enter, and arrow keys. Every link, button, and form field must be reachable and usable. 3 Test with a screen reader On Mac, use VoiceOver (Cmd+F5). On Windows, use NVDA (free download). Navigate your site and listen to how it is announced. You will quickly discover missing alt text, unclear link labels, and heading issues. 4 Check your colour contrast Use the WebAIM Contrast Checker or Chrome DevTools’ accessibility panel to verify all text meets the 4.5:1 contrast ratio requirement. 5 Validate
How to Optimise Your WordPress Site for Local SEO
How to Optimise Your WordPress Site for Local SEO | Simple Automation Solutions Home › Guides › WordPress Development WordPress Development How to Optimise Your WordPress Site for Local SEO Local search connects nearby customers to your business. Here is the complete WordPress local SEO framework — from Google Business Profile to LocalBusiness schema to location pages. SAS Simple Automation Solutions ·2026-03-21 ·⏱ 10 min read 46% of Google searches have local intent 42% more direction requests with Google Business photos 3–6 months for initial local SEO results #1 local ranking factor: Google Business Profile In this guide What local SEO means for WordPress Google Business Profile setup LocalBusiness schema Location-specific pages Homepage for local intent Build local citations Frequently asked questions A local business website has a different goal from a national brand or e-commerce store: it needs to rank in local search results, communicate trust to nearby customers, and drive calls and footfall. WordPress, configured correctly for local SEO, is one of the most effective platforms for achieving this. What local SEO means for a WordPress site Local SEO is the practice of optimising your website to appear in search results for location-specific queries — searches like ‘plumber in Lahore’, ‘accountant near me’, or ‘best restaurant Islamabad’. These searches have strong commercial intent and convert at much higher rates than generic queries. For a WordPress site, local SEO involves four pillars: On-site signals — your NAP (Name, Address, Phone) information, location-specific content, and LocalBusiness schema markup Google Business Profile — your presence in Google Maps and the local pack (the map results that appear above organic results) Local citations — consistent NAP mentions across directories (Yelp, Yellow Pages, industry directories) Reviews — the volume and quality of Google reviews for your business Step 1 — Set up your Google Business Profile Your Google Business Profile (formerly Google My Business) is the most important local SEO asset — more impactful than your website for appearing in the local map pack. WordPress cannot do this for you; it must be set up at business.google.com. 1 Create or claim your Google Business Profile Go to business.google.com and sign in with your Google account. Search for your business name. If it exists, claim it. If not, create a new profile. 2 Complete every field in your profile Business name, category, address, phone, website URL (your WordPress site), opening hours, and a description. Incomplete profiles rank lower. Add photos — businesses with photos receive 42% more requests for directions. 3 Select the most specific category Choose the most specific primary category that describes your business. Category is the single most important ranking factor in the local pack. Add secondary categories where relevant. 4 Connect your WordPress site URL Add your full WordPress site URL to the profile. Ensure the URL is exactly as it appears on your site (with or without www, https://). Consistency matters. 5 Verify your listing Google will send a verification postcard, or offer phone/email verification. Complete verification — an unverified listing has limited visibility. Step 2 — Configure LocalBusiness schema on your WordPress site LocalBusiness schema tells Google the structured details of your business — name, address, phone, opening hours, price range, and geographic coordinates. This data enables rich search results and strengthens the connection between your website and your Google Business Profile. 💡 Use Rank Math for local schema Rank Math’s free tier includes a Local SEO module with a visual form for entering your business details. It generates the correct LocalBusiness JSON-LD and adds it to every page automatically — no coding required. 1 Install Rank Math and enable the Local SEO module Go to Rank Math → Dashboard → Modules and enable ‘Local SEO’. This adds a Local SEO settings panel. 2 Fill in your business details Go to Rank Math → Titles & Meta → Local SEO. Enter your business name, type, address, phone, opening hours, price range, and geo-coordinates (find these via Google Maps: right-click your location → Copy coordinates). 3 Set your business type Select the most specific LocalBusiness type from the dropdown (e.g., Restaurant, MedicalClinic, LegalService, AccountingService). The more specific, the more useful the schema is for Google. 4 Verify in Google’s Rich Results Test Test any page of your site at search.google.com/test/rich-results. You should see LocalBusiness schema detected with your business details populated correctly. Step 3 — Create location-specific pages If you serve multiple areas, create a dedicated page for each location or service area. Each page should target a specific geographic + service keyword (e.g., ‘WordPress Development in Lahore’, ‘Accountant Islamabad’). Each location page needs unique content — not just a copy with the city name swapped. Write about local context, local clients, or service specifics for that area Include the city name in the page title, H1, first paragraph, and URL slug Embed a Google Maps iframe showing your business location Include customer testimonials from that specific area where possible Add LocalBusiness schema to each location page with the specific address for that location ⚡ Duplicate location pages are a spam signal Creating 50 identical pages with only the city name changed is a local SEO tactic that Google now actively penalises. Each location page must have substantively unique content. If you cannot write unique content for a location, do not create a page for it. Step 4 — Optimise your homepage for local intent Your homepage is typically your highest-authority page and the first thing visitors see. For a local business, it needs to communicate location clearly: Include your city/region in your H1 or prominent subheading Place your full NAP (Name, Address, Phone) in the website header or hero section — visible above the fold Add your business hours near the contact information Include a map embed and a clear ‘Get Directions’ link Feature local trust signals — logos of local clients, mention of local awards or associations Step 5 — Build local citations A local citation is any online mention of your business’s NAP. Consistent citations
WordPress Multisite vs Separate Installs: Which Architecture Should You Choose?
WordPress Multisite vs Separate Installs: Which Architecture Should You Choose? | Simple Automation Solutions Home › Guides › WordPress Development WordPress Development WordPress Multisite vs Separate Installs: Which Architecture Should You Choose? One WordPress network or multiple independent sites? The decision shapes your security posture, operational overhead, and flexibility for years. Here is how to decide correctly. SAS Simple Automation Solutions ·2026-03-21 ·⏱ 8 min read 1 codebase powers all Multisite sites Risk isolation is the key argument for separate installs ManageWP bridges the gap for multiple installs Complex extraction is Multisite’s biggest downside In this guide Core difference When Multisite wins When separate installs win Side-by-side comparison Managing multiple installs efficiently Frequently asked questions If you need more than one WordPress website, you face a choice that many site owners get wrong: build a Multisite network, or maintain separate independent WordPress installations. The answer depends on your specific needs — and getting it wrong creates significant technical debt. The core difference A WordPress Multisite network is a single WordPress installation that hosts multiple websites from one codebase, one database, and one hosting account. A separate WordPress installation for each site means each one is completely independent — its own files, its own database, its own hosting. ⚡ Neither is universally better Multisite is genuinely better in specific situations. Separate installs are genuinely better in others. The decision comes down to how related the sites are and whether shared management overhead outweighs the added complexity of Multisite. When Multisite wins Multisite makes operational sense when the sites share enough in common that centralized management provides real efficiency: University or institution networks — a central IT team manages dozens of department sites (law.university.edu, medicine.university.edu) with shared themes and plugins Franchise or multi-location businesses — each location has its own site with local content, but shares global branding, plugins, and theme updates applied once network-wide Publishing networks — a media company running regional editions under one editorial infrastructure SaaS platforms with per-customer sites — each customer gets their own subdomain site, all provisioned and managed centrally Language/region variants — same brand, separate sites per language, managed from one dashboard When separate installs win Separate installs are the right choice far more often than many people expect: Sites for different clients — never put client sites on a Multisite network. A network-level problem or compromise affects all clients simultaneously Sites with very different technical requirements — Multisite forces all sites to share the same PHP version, plugin set, and server resources Sites you may want to sell or transfer — extracting a site from Multisite is complex; a separate install can be moved with a simple migration Sites needing different hosting tiers — a high-traffic site and a low-traffic site on the same Multisite network share resources, causing the small site to suffer during the large site’s traffic spikes Sites with different security requirements — on Multisite, a compromised plugin or theme update affects every site in the network instantly Side-by-side comparison Factor Multisite Separate installs Updates Apply once for all sites Must update each site individually (or use ManageWP) Hosting cost One hosting account for all sites Separate hosting per site (or shared account with multiple installs) Plugin management Install once, activate per site Install separately on each site Risk isolation Problem affects entire network Each site is isolated — problems don’t spread Site portability Complex to extract a site Easy to migrate to new hosting Performance isolation All sites share server resources Each site can have its own resources/host Setup complexity More complex to configure Standard WordPress setup Best for Related sites under one organisation Independent sites or client work Managing multiple separate WordPress installs efficiently The main operational argument for Multisite is centralized management. But with the right tools, managing multiple separate installs is nearly as efficient: Multi-site management ManageWP Manage updates, backups, uptime, and security across unlimited WordPress sites from one dashboard. Free tier covers most needs. The most popular solution for agencies managing multiple client sites. Alternative MainWP Self-hosted alternative to ManageWP. Your management data stays on your own server rather than a third-party platform. Free core plugin. Hosting solution Reseller Hosting A reseller hosting account lets you host multiple WordPress installs under one billing relationship, with separate cPanel accounts per site — independent but efficiently managed. The practical answer For most businesses and agencies: separate installs managed via ManageWP. Separate installs give you risk isolation, portability, and flexibility that Multisite cannot match. ManageWP eliminates the main operational downside of separate installs by letting you apply updates, run backups, and monitor all sites from a single dashboard. Reserve Multisite for genuine institutional or platform use cases where sites are deeply interdependent and managed by a central technical team. Need help architecting your WordPress setup? Simple Automation Solutions advises on WordPress architecture, Multisite configuration, and multi-site management for organisations worldwide. Book a Free Call View Our Work → Frequently asked questions Can I convert a Multisite network to separate installs?+ Yes, but it requires effort per site. Each site must be exported from the network (using a plugin like NS Cloner or manual database extraction), then imported into its own fresh WordPress installation. URLs, user accounts, and media files require careful migration. For large networks this is a significant project — plan it thoroughly before starting. Does WordPress Multisite cost more to host?+ Not inherently — one Multisite installation runs on one hosting account. However, as the network grows, resource demands increase. A network of 20 active sites needs a hosting plan that can handle the combined traffic and database load of all 20 sites. Managed WordPress hosts (Kinsta, WP Engine) offer Multisite-specific plans with appropriate resources. Is WordPress Multisite good for SEO?+ Each site in a Multisite network has its own URL, its own Search Console property, and its own SEO configuration — so SEO is managed per-site, not network-wide. From Google’s perspective, Multisite sites are treated as independent websites. The SEO implications of Multisite versus separate
How to Add Schema Markup to Your WordPress Site for Rich Results
How to Add Schema Markup to Your WordPress Site for Rich Results | Simple Automation Solutions Home › Guides › WordPress Development WordPress Development How to Add Schema Markup to Your WordPress Site for Rich Results Schema markup tells Google what your content means — and unlocks rich results that increase click-through rates. Here is how to add every major schema type to WordPress. SAS Simple Automation Solutions ·2026-03-21 ·⏱ 9 min read 20+ schema types supported by Rank Math FAQ schema most impactful for CTR Free Rank Math schema toolkit 48h typical time to see rich results In this guide What schema markup does Method 1 — Rank Math Method 2 — Yoast SEO Method 3 — Manual JSON-LD Verify after adding Frequently asked questions Search engines do not just read your content — they try to understand it. Schema markup gives Google structured, machine-readable context about your pages, enabling rich results in search: star ratings, FAQs, How-To steps, breadcrumbs, and event details. This guide covers every method for adding it to WordPress. What is Schema markup and what does it do? Schema markup is a vocabulary of tags (defined at schema.org) that you add to your HTML to tell search engines what your content represents — an article, a product, a FAQ, a recipe, a local business. Google uses this structured data to generate rich results — enhanced search listings that stand out visually and typically attract higher click-through rates. Schema type What it enables in Google Best for Article Article rich result with date and author Blog posts, guides FAQPage Expandable FAQ directly in search results Any page with Q&A HowTo Step-by-step instructions in search results Tutorial posts Product Price, availability, star ratings in results WooCommerce products LocalBusiness Map panel, hours, phone in search Service businesses BreadcrumbList Breadcrumb path shown in results All pages ⚡ FAQ schema is the highest-value quick win Adding FAQPage schema to your existing blog posts can generate expandable FAQ panels directly in Google search results — dramatically increasing the visual space your result occupies and improving click-through rates. It takes under 10 minutes with Rank Math. Method 1 — Rank Math (recommended) Rank Math includes the most comprehensive Schema toolkit of any free SEO plugin. It supports 20+ schema types and adds them through a visual interface — no code required. 1 Install Rank Math and complete setup Go to Plugins → Add New, search Rank Math, install and activate. Run the setup wizard. Connect your Google account if prompted. 2 Open any post and find the Schema tab In the Gutenberg editor, click the Rank Math icon in the top toolbar. Navigate to the Schema tab (the last icon). Rank Math automatically adds Article schema to posts. 3 Add FAQ schema to posts with Q&A sections Click ‘Add Schema’, select ‘FAQ Page’. A form appears where you add each question and answer. Rank Math generates the correct JSON-LD and injects it into the page head automatically. 4 Add HowTo schema to tutorial posts Click ‘Add Schema’, select ‘How To’. Fill in the title, description, and each step. Rank Math handles the markup — no code needed. 5 Verify in Google’s Rich Results Test Go to search.google.com/test/rich-results, enter your page URL, and run the test. Google will show which schema types it detected and whether they are valid. Method 2 — Yoast SEO schema Yoast SEO automatically adds Article, WebPage, and BreadcrumbList schema to every page. For more specific schema types (FAQ, HowTo, Product), you need Yoast SEO Premium or a supplementary schema plugin. Go to Yoast SEO → Search Appearance → Content Types to configure the default schema type per post type On individual posts, the Yoast SEO meta box includes a Schema tab where you can set the page type and article type Yoast generates Organization schema for your site automatically based on your site settings — add your logo, social profiles, and business type For FAQ schema with Yoast Free: use the Yoast FAQ block in Gutenberg. Adding the Yoast FAQ block automatically generates FAQPage schema for that section Method 3 — Manual JSON-LD in a code block For advanced users, you can add schema markup manually by inserting a JSON-LD script block directly into a post using a Custom HTML block in Gutenberg or a code block in Elementor. 💡 JSON-LD is Google’s preferred format Google recommends JSON-LD for schema markup because it can be placed anywhere in the page (usually in the head or at the bottom of the body) without mixing with your visible HTML content. It is the cleanest implementation method. A minimal FAQPage JSON-LD example: create a Custom HTML block, paste the script tag with your @type:FAQPage object, and publish. Google will detect it on the next crawl. What to verify after adding schema 1 Run Google’s Rich Results Test Visit search.google.com/test/rich-results, enter your URL, and check for errors or warnings on each schema type. 2 Check Google Search Console for schema errors Go to Search Console → Enhancements. After a few days, Google reports how many pages with each schema type were found and flags any errors that prevent rich results from showing. 3 Monitor click-through rate changes After rich results begin appearing (can take 2–6 weeks), compare CTR in Search Console for schema-enabled pages versus the prior period. FAQ schema typically increases CTR by 20–40% for competitive queries. Need schema markup and technical SEO set up correctly on your WordPress site? Simple Automation Solutions configures schema, sitemap, and full technical SEO for WordPress sites worldwide — built to earn rich results from day one. Book a Free Call View Our Work → Frequently asked questions Does schema markup directly improve my Google rankings?+ Schema markup does not directly affect ranking positions. What it does is enable rich results — enhanced search listings with FAQ panels, star ratings, or step-by-step instructions. These rich results attract more clicks from the same position, improving your click-through rate. Higher CTR sends a positive engagement signal
WordPress Image Optimisation: How to Make Your Images Fast Without Losing Quality
WordPress Image Optimisation: How to Make Your Images Fast Without Losing Quality | Simple Automation Solutions Home › Guides › WordPress Development WordPress Development WordPress Image Optimisation: How to Make Your Images Fast Without Losing Quality Images are the biggest cause of slow WordPress sites. Here is the complete framework for compressing, converting, and serving images at maximum speed without visible quality loss. SAS Simple Automation Solutions · 2026-03-21 · ⏱ 10 min read 40% average page weight reduction after optimisation WebP 25–35% smaller than JPEG 5.5+ WordPress version with native lazy loading LCP most improved metric from image optimisation In this guide Why image optimisation matters Choose the right file format Compress before and after upload Enable WebP conversion Enable lazy loading Set explicit image dimensions Recommended workflow Frequently asked questions Images are almost always the heaviest content on a WordPress page — and the biggest single cause of slow load times. A homepage hero image uploaded at 4MB can delay your Largest Contentful Paint by 3–5 seconds on mobile. Image optimisation is the highest-leverage speed improvement available to most WordPress sites. Why image optimisation matters for WordPress Metric affected How unoptimised images hurt it Target Largest Contentful Paint (LCP) Hero image takes too long to load Under 2.5 seconds Cumulative Layout Shift (CLS) Images without set dimensions cause layout jumps Under 0.1 Total page weight Large images inflate the total data transferred Under 1MB total for most pages Mobile performance Mobile connections are slower — large images hit harder Score 70+ on PageSpeed mobile Bandwidth costs Large images increase server bandwidth usage Reduce with compression + CDN Step 1 — Choose the right file format The format you save an image in before uploading to WordPress is the first decision — and it has the biggest impact on file size. Format Best for Approximate size vs JPEG JPEG / JPG Photographs and complex images with gradients Baseline PNG Images with transparency, logos, screenshots 20–60% larger than JPEG WebP Everything — modern browsers support it universally 25–35% smaller than JPEG, 25% smaller than PNG AVIF Next-gen format — even smaller than WebP 40–50% smaller than JPEG (limited plugin support in 2026) SVG Logos, icons, simple graphics Vector — scales without quality loss, tiny file size 💡 Use WebP for everything in 2026 WebP is supported by all modern browsers and offers 25–35% smaller file sizes than JPEG at equivalent visual quality. Both Smush and ShortPixel convert your existing images to WebP automatically. Start serving WebP and your images get smaller without any change in visual appearance. Step 2 — Compress images before and after upload Compression removes unnecessary data from image files without visible quality loss. There are two types: Lossless compression — removes metadata and redundant data without changing any pixels. PNG files benefit most. No visible quality change. Lossy compression — reduces image quality slightly (at controlled levels) to achieve much larger file size reductions. At 80–85% quality setting, most viewers cannot see the difference. For WordPress, the practical workflow is: 1 Resize before uploading Never upload a 4000px wide image if your content column is 800px wide. Resize in an editor (Photoshop, GIMP, Squoosh.app) before uploading. WordPress generates multiple sizes from your upload, but the original is also stored — resizing first reduces the stored original size. 2 Set a max upload size in WordPress Add add_filter(‘big_image_size_threshold’, function(){ return 1200; }); to your child theme’s functions.php. This tells WordPress to automatically downscale any image uploaded larger than 1200px wide, preventing oversized originals from being stored. 3 Use an image compression plugin for automatic optimisation Install Smush or ShortPixel. These plugins automatically compress every image you upload and can bulk-optimise your existing media library. Set up once; works silently on every future upload. Step 3 — Enable WebP conversion WebP conversion takes your existing JPEG and PNG images and creates WebP copies. WordPress then serves WebP to browsers that support it (all modern browsers) and falls back to the original for older browsers. Free / Pro Smush Converts images to WebP on upload and stores both versions. Free version converts images up to 5MB. Pro tier adds CDN delivery and automatic lazy loading with WebP. Free / Pro ShortPixel Excellent WebP conversion quality. Processes 100 images per month free. One of the most popular compression plugins with strong support for AVIF as well as WebP. Free / Pro Imagify By the WP Rocket team. Tight integration with WP Rocket’s caching. Converts to WebP and serves via a smart picture element that falls back gracefully. Step 4 — Enable lazy loading Lazy loading tells the browser not to download images that are below the fold until the user scrolls toward them. On a page with 20 images, this means only the first 2–3 images load initially — dramatically reducing initial page weight. WordPress has native lazy loading built in since version 5.5 — the loading=”lazy” attribute is automatically added to all images inserted via the editor. However, images added via CSS backgrounds or custom code do not benefit from native lazy loading. Verify native lazy loading is active: view source on any post and check for loading=”lazy” on img tags For CSS background images, WP Rocket’s ‘Lazy load background images’ setting covers these Do not lazy load your LCP image — the hero image or first visible image should load immediately. Add loading=”eager” to your LCP image to override lazy loading for it Smush Pro adds lazy loading to any image not already covered by WordPress’s native implementation Step 5 — Set explicit image dimensions Cumulative Layout Shift (CLS) — when page elements move as images load — is often caused by images without explicit width and height attributes. The browser cannot reserve the correct space without these dimensions, so the layout shifts when the image arrives. WordPress 5.5+ automatically adds width and height attributes to images inserted via the Gutenberg editor. For images in custom code, page builders, or widget areas, verify the attributes are present
The Complete WordPress Maintenance Checklist: Weekly, Monthly, and Annual Tasks
The Complete WordPress Maintenance Checklist: Weekly, Monthly, and Annual Tasks | Simple Automation Solutions Home › Guides › WordPress Development WordPress Development The Complete WordPress Maintenance Checklist: Weekly, Monthly, and Annual Tasks A structured maintenance routine is the difference between a WordPress site that grows and one that accumulates technical debt. Here is every task, organised by how often to do it. SAS Simple Automation Solutions · 2026-03-21 · ⏱ 10 min read 55% of hacked WP sites ran outdated software 20 min weekly maintenance time 45 min monthly maintenance time Annual full audit and strategic review In this guide Weekly maintenance tasks Monthly maintenance tasks Annual maintenance tasks Maintenance tools to install When to hire a professional Frequently asked questions A WordPress site is not a set-and-forget asset. The sites that stay fast, secure, and high-ranking over time are the ones that receive consistent, structured maintenance. This checklist gives you a clear, frequency-based framework for every task. ⚡ Why maintenance matters Over 55% of successfully hacked WordPress sites were running outdated software at the time of the breach. Regular maintenance is not optional — it is the difference between a site that builds equity over time and one that becomes a liability. Weekly maintenance tasks These tasks take 10–20 minutes per week and catch problems before they become serious. 1 Check for WordPress core, plugin, and theme updates Go to Dashboard → Updates. Review any available updates. Apply security releases immediately. For major version updates, apply them to a staging environment first if you have one. 2 Review your backup status Open UpdraftPlus (or your backup plugin) and confirm last backup completed successfully. Check that the backup file was sent to off-site storage (Google Drive, S3, Dropbox). A backup stuck on your server is a single point of failure. 3 Check your site loads correctly Visit your homepage, a blog post, and your contact page. Click through any key user journeys. Confirm your contact form submits and you receive the notification email. 4 Review Google Search Console for errors Log into Search Console and check the Coverage report for new crawl errors and the Core Web Vitals report for new failing URLs. Address critical errors promptly. 5 Moderate comments and spam Approve genuine comments, delete spam. If you use Akismet, empty the spam queue weekly so it does not bloat your database. Monthly maintenance tasks Monthly tasks keep your site performing well over the medium term and catch slow-building issues before they become significant. 1 Run a full site speed test Run your homepage through Google PageSpeed Insights and GTmetrix. Compare against last month’s scores. If scores have dropped, identify what changed — a new plugin, a new large image, or increased page complexity. 2 Optimise your database Use WP-Optimise or the database tool in your hosting control panel to remove post revisions (keep last 3–5), clear transients, remove spam comments, and optimise database tables. On an active site this can recover 50–200MB of database storage. 3 Audit your plugins Review all installed plugins. Remove any that are deactivated or unused. Check that all active plugins have been updated in the last 60 days — plugins not updated in 90+ days may be abandoned and represent a security risk. 4 Review your 404 error log Install the Redirection plugin and review any 404 errors accumulated over the month. Set up 301 redirects for any broken URLs that are getting traffic — especially old URLs you may have changed. 5 Check site uptime records If you use UptimeRobot (free) or a similar monitor, review the month’s uptime report. Identify any downtime events and investigate their cause with your host. 6 Test your restore process At least once per month, download a backup file and verify it is not corrupted. Quarterly, do a full test restore to a staging environment to confirm your restore process actually works. Annual maintenance tasks Annual tasks address bigger-picture site health, content quality, and strategic alignment. 1 Conduct a full content audit Review all published posts and pages. Identify content that is outdated and needs updating, thin content that should be expanded or removed, and posts that have dropped in rankings and are candidates for optimisation. 2 Review and renew your domain and hosting Ensure your domain registration does not expire. Review your hosting plan — if your traffic has grown significantly, you may need to upgrade. Evaluate whether your current host is still the best fit for your needs. 3 Review your SSL certificate Most SSL certificates auto-renew via Let’s Encrypt. Verify the certificate is valid and not expiring. Check that HTTPS is enforced site-wide and there are no mixed content warnings. 4 Audit user accounts Go to Users → All Users. Remove any accounts that belong to former employees, contractors, or collaborators who no longer need access. Ensure no account has a higher access level than necessary. 5 Review and clean your media library Use the Media Cleaner plugin to identify and remove unused media files (images not attached to any post or page). On an active site this can free significant server storage. 6 Assess your SEO performance annually Review 12 months of Google Search Console data. Which queries are you ranking for? Which pages drive the most traffic? Where have rankings dropped? Use this to plan your content strategy for the coming year. Maintenance tools worth installing Backup UpdraftPlus Automated backups to off-site cloud storage. Free version handles all essential backup needs for most sites. Database WP-Optimise One-click database cleaning — removes revisions, spam, transients, and optimises tables. Schedule automatic monthly runs. Security Wordfence Automated malware scanning, firewall, and login protection. Weekly scan emails keep you informed of any threats detected. Uptime UptimeRobot Free uptime monitoring — pings your site every 5 minutes and emails you instantly if it goes down. Takes 2 minutes to set up. Redirects Redirection Logs 404 errors and lets you create 301 redirects from the WordPress dashboard. Essential for tracking broken links. Updates ManageWP Manage updates,
How to Create a High-Converting Landing Page in WordPress
How to Create a High-Converting Landing Page in WordPress | Simple Automation Solutions Home › Guides › WordPress Development WordPress Development How to Create a High-Converting Landing Page in WordPress A landing page has one job: convert visitors into leads or customers. Here is the complete framework — from page builder setup to copy principles to technical configuration. SAS Simple Automation Solutions · 2026-03-21 · ⏱ 11 min read 1 goal per landing page 7 essential sections every page needs 60% of landing page traffic is mobile 3–8% typical conversion rate range In this guide Landing page vs regular page Choose your page builder Set up the page structure The 7 essential sections Copywriting principles Technical setup for conversions Frequently asked questions A landing page has one job: convert visitors into leads, customers, or subscribers. Unlike a homepage or service page, a landing page removes every distraction and focuses the visitor’s attention on a single action. Done correctly, it is one of the highest-ROI pages on your entire website. Landing page vs regular page — the key differences Element Regular page Landing page Navigation menu Full site navigation Removed or minimised Goal Multiple actions possible Single, specific CTA only Footer Full footer with links Minimal or removed Content General information Focused on one offer or action Sidebar Often present Always removed Links to other pages Many None or minimal Step 1 — Choose your page builder WordPress’s default Gutenberg editor can produce a functional landing page, but dedicated page builders give you more layout control and purpose-built elements (countdown timers, testimonial blocks, opt-in forms). Free + Pro Elementor The most widely used landing page builder for WordPress. Its free version handles most landing page needs. Pro adds popups, countdown timers, form widgets, and WooCommerce product elements. Free + Pro Kadence Blocks Built on Gutenberg. Excellent for clean, fast landing pages with custom sections, testimonials, and call-to-action blocks. Lighter than Elementor with strong Core Web Vitals scores. Premium Divi Builder Includes 200+ landing page templates. Strong A/B testing built in — test headlines, CTAs, and layouts without a separate plugin. Best if you are already using Divi as your theme. Step 2 — Set up the page structure 1 Create a new page and set a full-width template Go to Pages → Add New. In the Page Attributes panel, set the template to ‘Full Width’ or ‘Canvas’ (the name varies by theme). This removes the sidebar and often the header/footer — giving you a blank canvas. 2 Open in your page builder Click ‘Edit with Elementor’ (or your chosen builder). Start from a blank canvas rather than a template — templates train you to copy rather than think about your specific offer and audience. 3 Set the page width to 1200px maximum In Elementor’s Site Settings or section settings, set the content width to 1000–1200px. Wider than this and line lengths become hard to read on desktop. 4 Hide the header and footer For a true landing page, remove site navigation. In Elementor, use the ‘Hide Header’ and ‘Hide Footer’ options in the page settings. In Kadence, use the ‘Transparent Header’ or ‘No Header’ header layout option. Step 3 — The 7 essential sections Every high-converting landing page follows a proven structure. These seven sections, in order, guide the visitor from awareness to action. 1 — Hero section The first thing the visitor sees — must answer three questions in under 5 seconds: What is this? Who is it for? What do I do next? Headline: your core value proposition in one sentence. Specific beats clever. Sub-headline: expand the headline with a concrete benefit or qualification Primary CTA button: action-oriented text (‘Get Your Free Quote’, ‘Book a Call’, ‘Start Free Trial’) Hero image or short video: show the product, the result, or the person behind the service 2 — Social proof strip Immediately below the hero — logos of companies you have worked with, or a stat strip (40+ clients served, 4.9/5 average rating). Establishes credibility before the visitor has read anything. 3 — Problem statement Describe the pain your visitor is experiencing. If they recognise themselves in your problem description, they trust that you understand them — and are more likely to believe your solution. 4 — Solution and benefits Explain your offer and its benefits. Focus on outcomes, not features. ‘Your site loads in under 2 seconds’ not ‘We configure WP Rocket caching’. 5 — How it works A simple 3-step process block removes friction by making the path to getting the result feel easy and clear. 6 — Testimonials / case studies Real results from real clients are the most persuasive content on any landing page. Use full names and photos where possible. Specific results (‘increased traffic by 340% in 6 months’) outperform generic praise (‘great service!’). 7 — Final CTA Repeat your call to action at the bottom of the page. Visitors who read this far are your most interested prospects. Make it easy for them to act. Step 4 — Copywriting principles that increase conversions Speak to one person — write as if you are speaking directly to your ideal client, not a crowd Lead with the outcome — your reader does not care about your process; they care about the result they will get Use ‘you’ more than ‘we’ — every sentence focused on the visitor outperforms sentences focused on your company Reduce friction at the CTA — add micro-copy below your button that removes objections (‘No credit card required’, ‘Cancel anytime’, ‘Free 30-minute call’) One page, one goal — every link to another page is an exit. Keep the visitor focused on one action 💡 The most common landing page mistake Trying to explain everything on one page. The goal of a landing page is not to fully educate — it is to build enough trust and interest to get the visitor to take one specific action. Remove any section that does not directly move the visitor toward that action. Step 5 —
WordPress Caching Explained: How to Speed Up Your Site with WP Rocket and W3 Total Cache
WordPress Caching Explained: How to Speed Up Your Site with WP Rocket and W3 Total Cache | Simple Automation Solutions Home › Guides › WordPress Development WordPress Development WordPress Caching Explained: How to Speed Up Your Site with WP Rocket and W3 Total Cache Caching is the single most impactful speed optimisation you can make on WordPress. Here is how it works and how to configure it correctly. SAS Simple Automation Solutions · 2026-03-21 · ⏱ 10 min read 80% typical TTFB improvement from page caching $59 WP Rocket per year — one site Free W3 Total Cache — always 200ms achievable TTFB with caching on good hosting In this guide What WordPress caching does WP Rocket — premium standard W3 Total Cache — free alternative What not to do with caching Frequently asked questions Without caching, WordPress rebuilds every page from scratch for every visitor — querying the database, running PHP, and assembling HTML before sending anything to the browser. On a busy site this is slow and resource-intensive. Caching solves this by storing pre-built page copies and serving them instantly. What WordPress caching actually does When a visitor loads your homepage without caching, WordPress executes PHP, runs 20–60 database queries, and assembles the HTML — this takes 500ms–3 seconds depending on your server. With caching, WordPress does this once, saves the resulting HTML file, and serves that saved file to every subsequent visitor — taking 10–50ms instead. There are several layers of caching, each addressing a different bottleneck: Cache type What it stores Speed improvement Page cache Full HTML of each page Largest — 80–95% faster TTFB Browser cache Static files in visitor’s browser Eliminates repeat downloads Object cache Database query results Significant for dynamic pages CDN cache Static assets on edge servers Reduces global latency Opcode cache Compiled PHP bytecode Server-level — usually pre-configured ⚡ Start with page caching Page caching delivers the largest speed improvement of any optimisation you can make on WordPress. If you do nothing else, enable page caching. It turns a 2–3 second page load into a 200–400ms page load on most servers. WP Rocket — the premium standard WP Rocket is the most widely recommended caching plugin for WordPress. It activates page caching automatically on installation with sensible defaults, and its interface is clean enough that non-developers can configure it correctly within minutes. Cost: $59/year for one site, $119/year for three sites, $299/year for unlimited sites. Recommended WP Rocket settings 1 Cache tab — enable all three cache options Enable ‘Enable caching for mobile devices’ and ‘User Cache’. Leave ‘Cache Lifespan’ at 10 hours for most sites — lower it to 2–4 hours if you publish content multiple times per day. 2 File Optimisation — minify CSS and JS Enable ‘Minify CSS files’ and ‘Minify JavaScript files’. Enable ‘Combine CSS files’. Be cautious with ‘Combine JS’ — test your site after enabling it as it occasionally breaks scripts. Enable ‘Defer JavaScript execution’. 3 Media — enable lazy loading Enable ‘Lazy load for images’ and ‘Lazy load for videos’. Enable ‘Add missing image dimensions’ to prevent layout shift (CLS). Enable WebP caching if you are serving WebP images. 4 Preload — enable sitemap-based preload Enable ‘Activate Preloading’ and ‘Preload Links’. Connect your sitemap URL so WP Rocket pre-warms the cache by crawling your sitemap after cache is cleared. 5 Advanced Rules — exclude dynamic pages Exclude any pages that should never be cached: your cart page, checkout page, account pages, and any page with personalised content. Add their URLs to the ‘Never Cache These Pages’ field. W3 Total Cache — the free alternative W3 Total Cache (W3TC) is the most powerful free caching plugin for WordPress. It offers more granular control than WP Rocket but requires more configuration to get right. It is the right choice if you need a free solution or want fine-grained control over caching behaviour. W3TC essential settings for beginners 1 General Settings — enable Page Cache Go to Performance → General Settings. Enable ‘Page Cache’ and set the method to ‘Disk: Enhanced’ — this is the most compatible option for shared hosting. Enable ‘Database Cache’ set to ‘Disk’ and ‘Object Cache’ set to ‘Disk’. 2 Page Cache settings Go to Performance → Page Cache. Enable ‘Cache front page’, ‘Cache feeds’, and ‘Cache SSL’. Set ‘Garbage collection interval’ to 3600 seconds (1 hour). Add your cart and checkout pages to the ‘Never cache these pages’ list. 3 Browser Cache settings Go to Performance → Browser Cache. Enable ‘Set Last-Modified header’, ‘Set expires header’, and ‘Enable HTTP (gzip) compression’. Set the CSS and JS expiry to 1 year (31536000 seconds). 4 Minify settings Go to Performance → Minify. Enable ‘Rewrite URL structure’. For CSS, set ‘Minify’ to Auto. For JS, test carefully — use Manual mode if Auto breaks your site’s scripts. 💡 W3TC vs WP Rocket in practice W3 Total Cache configured correctly matches WP Rocket’s performance on most metrics. The difference is the time it takes to configure — WP Rocket takes 10 minutes to a working setup; W3TC takes 30–60 minutes and requires testing. For non-developers, WP Rocket’s $59/year cost is justified by the time saved. What not to do with WordPress caching Never run two caching plugins simultaneously — they conflict and cause blank pages or broken layouts. Pick one. Do not cache logged-in users — admin users and logged-in customers see personalised content. Both plugins exclude logged-in users by default; verify this setting is on. Do not cache WooCommerce cart/checkout pages — these pages are dynamically generated per user. Caching them causes cart contents to bleed between users. Clear cache after every content update — both plugins can be set to automatically clear the cache for a page when it is updated. Enable this to ensure visitors always see fresh content. Want your WordPress site configured for maximum speed? Simple Automation Solutions sets up caching, image optimisation, and CDN for WordPress sites worldwide — delivering measurable Core Web Vitals improvements. Book a Free Call
How to Add Google Analytics 4 to WordPress: 3 Methods Compared
How to Add Google Analytics 4 to WordPress: 3 Methods Compared | Simple Automation Solutions Home › Guides › WordPress Development WordPress Development How to Add Google Analytics 4 to WordPress: 3 Methods Compared GA4 is the only way to understand how visitors use your site. Here are the three methods for connecting it to WordPress — with a clear recommendation for each type of user. SAS Simple Automation Solutions · 2026-03-21 · ⏱ 9 min read GA4 current Google Analytics version Free to set up and use 30s to verify live in Realtime 3 methods — plugin, code, GTM In this guide What is GA4 and why it matters Create your GA4 property Method 1 — Plugin Method 2 — Manual code Method 3 — Google Tag Manager Verify enhanced measurement Frequently asked questions You cannot improve what you do not measure. Google Analytics 4 tells you where your visitors come from, which pages they read, how long they stay, and what actions they take. This guide covers every method for connecting it to WordPress — and which one to use. What is Google Analytics 4 and why upgrade from UA? Google Analytics 4 (GA4) is the current version of Google Analytics. Universal Analytics (UA) was permanently shut down on 1 July 2024 — if you are still seeing UA data anywhere, it is historical. All new tracking must be done through GA4. GA4 uses an event-based data model instead of UA’s session-based model. Every interaction — page view, scroll, click, form submission, video play — is tracked as an event with associated parameters. This gives you significantly more granular data about how users actually engage with your content. Step 1 — Create your GA4 property 1 Go to analytics.google.com Sign in with your Google account. If you are new to Analytics, click ‘Start measuring’. If you have an existing account, click the gear icon (Admin) in the bottom left. 2 Create a new property Click ‘Create Property’. Enter your website name, select your reporting time zone and currency, then click Next. Fill in your business details and click Create. 3 Set up a Web data stream Select ‘Web’ as your platform. Enter your website URL and stream name. Click ‘Create stream’. You will see your Measurement ID — it looks like G-XXXXXXXXXX. Copy it. You need this for all three methods below. Method 1 — Plugin (recommended for most sites) A dedicated plugin is the simplest, most reliable method. It handles the code insertion correctly and usually adds enhanced measurement features on top of the standard GA4 tag. Free — Best Option Google Site Kit Official plugin by Google. Connects GA4, Search Console, PageSpeed Insights, and AdSense in one dashboard. Verifies your site with Google automatically. Recommended for beginners. Free / Premium MonsterInsights Shows GA4 data directly inside your WordPress dashboard. Tracks forms, WooCommerce, and custom events without code. The most feature-rich GA4 plugin for WordPress. Free GA Google Analytics Lightweight plugin — just inserts the GA4 tag. No frills, minimal overhead. Good for advanced users who only need the basic tag inserted. 1 Install your chosen plugin Go to Plugins → Add New, search for your chosen plugin, install and activate it. 2 Connect your Google account Follow the plugin’s setup wizard. You will be prompted to sign in with Google and grant permissions to access your Analytics account. 3 Select your GA4 property Choose the GA4 property you created in Step 1. The plugin will insert the tracking code on every page of your site automatically. 4 Verify tracking is working Open your website in a browser, then go to GA4 → Reports → Realtime. You should see your visit appear within 30 seconds. If you see data, tracking is live. Method 2 — Manual code in your theme If you prefer not to use a plugin, you can insert the GA4 tracking code directly into your theme’s header. This is the lightest-weight method — no plugin overhead — but it requires a child theme so the code is not erased when your theme updates. ⚡ Prerequisite You must be using a child theme before adding code to functions.php or header.php. If you add code to your parent theme files directly, a theme update will delete it. See our WordPress Child Themes guide for setup instructions. 1 Copy your GA4 code snippet In GA4, go to Admin → Data Streams → your stream → View tag instructions. Copy the full JavaScript snippet — it starts with . 2 Add the code to your child theme’s functions.php Open your child theme’s functions.php and add this function: wp_head() fires the snippet on every page inside the tag, which is exactly where GA4 needs to load. 3 Or paste directly into header.php Alternatively, open your child theme’s header.php, find the closing tag, and paste the GA4 snippet immediately before it. 4 Verify in GA4 Realtime Visit your site and check GA4 → Realtime to confirm the tag is firing correctly. 💡 Use functions.php, not header.php Adding code via functions.php using wp_enqueue or wp_head hooks is cleaner than editing header.php directly. It keeps your tracking code separate from your template markup and is easier to manage. Method 3 — Google Tag Manager Google Tag Manager (GTM) is a tag management system that lets you deploy and manage tracking scripts from a single web interface — without editing your website code every time you add a new tag. It is the professional standard for sites with multiple tracking needs. With GTM, you install one GTM container snippet on your site (via plugin or manual code). Every subsequent tracking tag — GA4, Facebook Pixel, LinkedIn Insight, custom event tracking — is managed from the GTM dashboard without touching WordPress at all. Best for: sites running multiple tracking scripts, agencies managing multiple clients, or anyone who needs to add/modify tracking frequently Use the GTM4WP plugin to insert the GTM container code into WordPress correctly (including the noscript fallback) Once GTM is installed,
Setup XML Sitemap in WordPress
How to Set Up an XML Sitemap in WordPress | Simple Automation Solutions Home › Guides › WordPress Development WordPress Development How to Set Up an XML Sitemap in WordPress and Submit It to Google An XML sitemap tells Google exactly what pages exist on your site and how often they change. Here is how to generate one, configure it correctly, and get it indexed fast. SAS Simple Automation Solutions · March 21, 2026 · ⏱ 8 min read XML machine-readable format Google prefers Free auto-generated by Yoast & Rank Math 48h typical time for Google to start crawling 1 URL to submit in Search Console In this guide What is an XML sitemap and why does it matter? Generate a sitemap with Yoast SEO Generate a sitemap with Rank Math What to include and exclude Submit your sitemap to Google Search Console Submit to Bing Webmaster Tools Monitor and maintain your sitemap Frequently asked questions A sitemap does not directly improve your rankings. What it does is make sure Google can find, crawl, and index every page you want ranked — reliably and quickly. For a new site or a large site with deep page structures, it is one of the highest-leverage technical SEO tasks you can complete in under 30 minutes. What is an XML sitemap and why does it matter? An XML sitemap is a file that lists every URL on your website that you want search engines to know about. It is written in a structured format that Google, Bing, and other search engines can read automatically. Think of it as a table of contents you hand directly to Googlebot. Without a sitemap, Google discovers your pages by following links — starting from your homepage and crawling outward. For small, well-linked sites this is usually sufficient. But for sites with: Many pages not linked from the main navigation Frequently updated content (blog posts, product pages) New sites with little external authority Large e-commerce catalogues …a sitemap ensures nothing slips through the cracks. ⚡ What a sitemap does not do Submitting a sitemap does not guarantee that Google indexes every URL in it. Google still decides what to crawl and index based on quality signals. A sitemap removes the discovery barrier — it does not remove the quality barrier. Pages that are thin, duplicate, or noindexed will still not rank regardless of whether they are in your sitemap. Generate a sitemap with Yoast SEO Yoast SEO generates an XML sitemap automatically as soon as it is activated. You do not need to do anything to create it — it exists at yourdomain.com/sitemap_index.xml by default. To verify it is enabled and configure what it includes: 1 Go to Yoast SEO → Settings In your WordPress dashboard, click on “Yoast SEO” in the left sidebar, then click “Settings” at the top of the Yoast panel. 2 Navigate to the Site Features tab Click “Site features” in the Yoast settings sidebar. Scroll to “XML sitemaps” and confirm the toggle is switched on. 3 Configure which content types appear Go to “Content types” in the Yoast settings. For each post type and taxonomy, you can toggle whether it appears in the sitemap. Set any content type you have marked as “noindex” to be excluded from the sitemap. 4 View your sitemap index Visit yourdomain.com/sitemap_index.xml in your browser. You will see sub-sitemaps listed for posts, pages, categories, and any custom post types. This is the URL you submit to Google. 💡 Yoast sitemap structure Yoast generates a sitemap index — a parent file that links to individual sub-sitemaps for each content type (post-sitemap.xml, page-sitemap.xml, etc.). Submit only the index URL (/sitemap_index.xml) to Google Search Console — Google will find and process all sub-sitemaps automatically. Generate a sitemap with Rank Math Rank Math also generates a sitemap automatically. By default your sitemap is at yourdomain.com/sitemap_index.xml — the same URL as Yoast. If you switch between plugins, the URL stays consistent. 1 Go to Rank Math → Sitemap Settings In your WordPress dashboard, go to Rank Math → Sitemap Settings. This panel gives you full control over everything the sitemap includes. 2 Enable the sitemap module If the Sitemap module is not already active, go to Rank Math → Dashboard → Modules and toggle “Sitemap” on. 3 Configure included content types In Sitemap Settings, you will see toggles for Posts, Pages, Categories, Tags, and any custom post types. Enable only content types you want Google to index. Exclude author archives and date archives unless they contain unique value. 4 Set the images option Rank Math lets you include images in your sitemap. Enable this — it helps Google discover images for Google Image Search and can drive additional organic traffic. What to include and exclude from your sitemap Not every URL on your site should be in your sitemap. Including low-quality or noindexed pages wastes crawl budget and can signal poor site quality to Google. Include in your sitemap All published blog posts and articles All key landing pages and service pages WooCommerce product pages and main category pages Your homepage, About page, Contact page Any page you actively want to rank on Google Exclude from your sitemap Pages marked noindex in your SEO plugin Thank-you pages and confirmation pages Login, register, and account pages Tag archives if they have thin content (fewer than 5 posts each) Paginated archive pages (/page/2/, /page/3/) Admin, search results, and 404 pages Content type Include in sitemap? Reason Published posts & pages Yes Core indexable content Product pages (WooCommerce) Yes Core e-commerce content Category archives Conditional Include if they have 5+ posts and unique descriptions Tag archives Usually no Often thin — noindex and exclude Author archives No Thin content; exclude unless multi-author site Search result pages No These should always be noindexed Login / checkout pages No Not indexable content Submit your sitemap to Google Search Console Generating a sitemap is only half the job. You need to actively tell Google where it is. Google Search