WordPress SEO 2026: checklist for Indian SMBs

WordPress SEO guide 2026: the complete checklist

WordPress powers roughly 40 percent of the web. That market share means two things: there is a plugin for every SEO task imaginable, and there is a long list of ways to get it wrong. Most WordPress SEO failures we audit trace back to the same five root causes: wrong hosting, an unconfigured SEO plugin, unoptimised images, missing schema, and no internal linking plan. This checklist covers all five.

1. Hosting and server setup

SEO starts at the server. A slow host cannot be fixed by a plugin.

Choose a host with Indian data centres or a CDN with Indian edge nodes. Time to First Byte (TTFB) is a Core Web Vitals component. If your visitors are in India and your server is in Frankfurt, you are adding 200 to 400 milliseconds to every page load for no reason. SiteGround, Cloudways, and WP Engine all offer India-optimised infrastructure or Cloudflare integration with Indian PoPs. Our Core Web Vitals 90-day plan covers the Indian-specific device and network conditions that affect LCP, INP and CLS — and how to fix them in 90 days.

Use PHP 8.2 or newer. WordPress 6.4+ runs best on PHP 8.2. Older PHP versions are slower and receive no security patches.

Enable HTTP/3 and BoringSSL. These protocols reduce connection setup time, especially on mobile networks common in India.

Install W3 Total Cache or WP Super Cache. Server-side page caching reduces TTFB dramatically. If your host offers built-in caching (most managed WordPress hosts do), use that instead and skip the plugin.

Set up a CDN. Cloudflare’s free plan is sufficient for most Indian SMB sites. It handles SSL termination, serves static assets from the nearest edge node, and blocks a significant proportion of malicious traffic before it reaches your server.

2. SEO plugin setup

Install one SEO plugin. Not two. Not the one your theme came with. One.

Rank Math and Yoast SEO are the two credible options in 2026. Both generate XML sitemaps, manage canonical URLs, handle schema markup, and redirect old URLs after a site move. Rank Math includes those features out of the box. Yoast requires fewer decisions but more extensions for advanced schema.

Whatever you choose, configure these settings before publishing a single page:

Enable the XML sitemap. Submit it to Google Search Console. Check the “Discourage search engines from indexing this site” box only if you are building and not yet ready to be found. Keep the sitemap to indexable, 200-status URLs only.

Set a default title template. The pattern is: {post-title} | {site-name} for posts, {page-title} | {site-name} for pages. Avoid the {site-name} | {tagline} pattern — it wastes the most valuable real estate in the title tag.

Set a default meta description template. Include the primary keyword and a clear value proposition. The template should not produce the same description for every page.

Configure canonical URLs. Set them to automatic. Canonical tells Google which version of a URL is the master, which prevents duplicate content issues from URL parameters, pagination, and trailing slashes.

Enable breadcrumb markup. The BreadcrumbList schema that follows is picked up by Google for sitelinks and by AI search tools for page hierarchy.

3. On-page fundamentals

Once the plugin is configured, on-page SEO is mostly discipline.

Unique title and meta description on every page. This is the most commonly violated rule on WordPress sites we audit. Use the SEO plugin’s bulk editor to export all titles and descriptions. Any duplicate is a fix. Any blank is a priority fix.

One H1 per page. The page title (H1) should state the topic clearly and contain the primary keyword. If you use a page builder that wraps the title in a visual heading block, make sure it renders as a real <h1> tag, not a styled <div>.

URL structure. Use plain slugs that describe the page: /wordpress-seo-guide-2026 not /p=123. Enable “Strip category prefixes” in the SEO plugin if your posts live under /blog/. Keep slugs short, lowercase, and hyphenated.

Heading hierarchy. H1, then H2, then H3. No skipping levels. This is both an accessibility requirement and how search engines understand your page structure.

Image optimisation. This is the step most often skipped on Indian SMB WordPress sites. Every image needs three things before upload: compression (TinyPNG or ShortPixel), WebP format, and explicit width and height attributes on the <img> tag to prevent CLS. Use the ShortPixel or Imagify plugin to handle batch conversion of existing images, or run the folder through our image optimizer once before you install the plugin.

Alt text on every image. Write descriptive alt text that includes the primary keyword where natural. Do not stuff keywords into alt text.

Internal links. Add at least three contextual links per 1,000 words of body content. Link to related posts, service pages, and at least one resource in a different section of the site. Use descriptive anchor text, not “click here.” The on-page SEO checklist covers the full internal linking structure — cluster strategy, orphan detection, and anchor text rules — in more detail.

External links to authoritative sources. Linking to Wikipedia definitions, government resources, or official documentation adds credibility signal. Open external links in a new tab so readers do not leave your page.

4. Site speed and Core Web Vitals

Google uses Core Web Vitals as ranking signals. For WordPress, the three that most commonly fail are:

LCP (Largest Contentful Paint) under 2.5 seconds. The main culprit is a full-size hero image above the fold served without optimisation. Fix: compress the hero image to WebP, set explicit width and height, and add fetchpriority="high" to the image tag. If you use a page builder, disable “load all scripts on every page” and only load scripts on the pages that need them.

CLS (Cumulative Layout Shift) under 0.1. Caused by images without dimensions, ads loading above content, or web fonts causing text reflow. Fix: set width and height on every image. Reserve ad slot space with CSS. Use font-display: swap for web fonts.

INP (Interaction to Next Paint) under 200 milliseconds. Caused by heavy JavaScript blocking the main thread. WordPress plugins are the usual suspects. Use the Query Monitor plugin to identify which plugin is adding the most JavaScript. Deactivate and test in a staging environment before removing any plugin.

Run PageSpeed Insights on every major page type: homepage, service page, blog post. The homepage and top blog posts are the most critical. Target green on mobile. Our free Core Web Vitals tester gives you the three numbers without waiting on a field dataset.

5. Schema and structured data

Schema helps Google understand what is on your page. Without it, Google has to guess.

BreadcrumbList on every page. Most SEO plugins enable this by default. Confirm it is active in the schema settings.

FAQPage on informational pages. Every blog post and every service page should carry 6 to 12 FAQ questions with short, direct answers. The SEO plugin will generate the FAQPage schema block automatically.

LocalBusiness on service-area pages. If your client serves a specific Indian city or region, add LocalBusiness schema with the address, phone, opening hours, and geographic coordinates. This feeds the Google Business Profile and Maps integration.

Article schema on blog posts. Set articleSchema: Article in the plugin. Use the publish date as datePublished and the last update date as dateModified.

Validate your schema. Use Google’s Rich Results Test (search.google.com/test/rich-results) on your most important pages. Fix any errors before they compound. You can also run the markup through our schema markup generator before it goes live.

6. Mobile-first

More than 70 percent of Indian SMB website traffic comes from mobile. If your WordPress theme is not mobile-responsive, change the theme immediately.

Test on real Android hardware. Chrome DevTools device emulation is useful but not sufficient. Test on a real mid-range Android phone on a real 4G connection. If the page takes longer than three seconds to become readable, speed is your priority.

Remove tap-to-call blocks. On mobile, every phone number should be a tel: link. On service pages and the contact page, this is not optional — it is the primary conversion action for phone-capable visitors.

Responsive images. Serve different image sizes for mobile and desktop using the srcset attribute. Most image optimisation plugins handle this automatically.

7. Security and uptime

A hacked WordPress site gets deindexed. That is not a recovery scenario — it is a rebuild scenario.

Change the WordPress admin URL. The default /wp-admin path is scanned by bots on every hacked WordPress site on the internet. Use a plugin like WPS Hide Login to change it to something unique.

Use strong credentials and 2FA. Admin accounts need a strong unique password and two-factor authentication. Limit login attempts with a plugin like Limit Login Attempts Reloaded.

Keep WordPress, themes, and plugins updated. This is the single most effective security measure. Enable automatic updates for WordPress core. Review plugin updates within one week of release.

Install a WordPress-specific firewall. Wordfence or Sucuri both provide WordPress-specific threat detection that generic CDN firewalls miss.

Monitor uptime. Use UptimeRobot or Grafana to alert you when the site goes down. Google penalises sites with poor uptime availability.

8. Local SEO for WordPress sites

If your client serves a local Indian market, WordPress local SEO has a few specific requirements.

Google Business Profile is the foundation. The website should match the NAP (name, address, phone) on the GBP exactly. Every directory citation should match that same NAP. See our local SEO guide for Indian SMBs for the full GBP setup, citation strategy and 90-day local ranking plan.

Embed Google Maps on the contact page. Use an iframe embed, not a JavaScript map that slows the page down.

City or location in the page title and first 100 words. For a plumber in Bhavnagar, the homepage H1 should say “Bhavnagar” not just “Plumbing Services.” The first 100 words of body copy should mention the city or service area.

Schema reflects the service area. If the business covers multiple cities, use LocalBusiness schema with areaServed listing each city.

9. Content and maintenance habits

The technical checklist takes you to the starting line. The content and maintenance habits keep you there.

Audit titles and meta descriptions quarterly. Use the SEO plugin’s bulk editor to export all titles and descriptions to a spreadsheet. Flag any that are blank, duplicate, or over the character limit.

Refresh thin content. Pages under 400 words with no internal links are ranking liabilities, not assets. Expand them or redirect them to a more complete page on the same topic.

Update old statistics. If a blog post cites a 2021 study, note it in the post or replace it with a current source. Stale data damages credibility and is picked up by AI citation tools.

Monitor indexation in Google Search Console. Check the Pages report monthly. Any page marked “Discovered — currently not indexed” needs investigation. It usually means the page is thin, blocked by robots.txt, or orphaned with no internal links pointing to it. If the thin pages cluster around filters or tags, read our guide to faceted navigation crawl traps next.

Track Core Web Vitals monthly. Set a recurring calendar task. PageSpeed scores drift as plugins and content accumulate. A page that scored green in January may be red by July.

The checklist summary

1. Use a fast host with Indian data centres or a CDN with Indian edge nodes.
2. Run PHP 8.2 or newer.
3. Install one SEO plugin and configure it fully before publishing.
4. Set a unique title and meta description on every page.
5. Use plain, keyword-containing slugs.
6. One H1 per page. Correct heading hierarchy throughout.
7. Compress images to WebP before upload. Set width and height attributes.
8. Write alt text on every image.
9. Add three contextual internal links per 1,000 words of body content.
10. Enable BreadcrumbList schema and FAQPage schema on every informational page.
11. Run PageSpeed Insights on mobile for every major page type. Target green on all three Core Web Vitals.
12. Remove heavy page builder scripts from pages that do not use them.
13. Change the WordPress admin URL from the default.
14. Keep WordPress core, themes, and plugins updated automatically.
15. Install a WordPress-specific firewall.
16. Add LocalBusiness schema if the site serves a local Indian market.
17. Audit titles and meta descriptions in bulk every quarter.
18. Refresh thin content pages annually.
19. Monitor indexation in Google Search Console monthly.
20. Track Core Web Vitals monthly.

Work through this checklist in order. The top items — hosting, plugin setup, and images — have the highest impact. The bottom items — quarterly audits and maintenance habits — are what keep rankings stable over time.