
Your content can be excellent and still not rank. If Google cannot crawl your pages, cannot understand them, or finds them too slow on a phone, the best article in the world stays invisible. That is what this technical SEO checklist fixes — the behind-the-scenes health of your WordPress site, checked item by item, with the exact WordPress settings to change and free tools to verify each one.
Work through it in order. The first sections cover the things that can remove you from Google entirely; the later ones cover the things that push you up the rankings. Most items take minutes, and you only need to do the full pass once — then repeat a short version monthly.
✓Before You Start: The 10-Minute Baseline
Do not fix blind. Before touching anything, get three numbers so you know what actually needs work:
- Google Search Console: open the Pages report. Note how many pages are indexed, and how many sit under “not indexed” — and why (noindex, redirect, duplicate, “crawled but not indexed”).
- PageSpeed Insights: test your homepage and one key service page on mobile. Note the Core Web Vitals: LCP (loading), INP (responsiveness) and CLS (visual stability).
- A crawl of your own site: the free version of Screaming Frog (up to 500 URLs) or the free Ahrefs Webmaster Tools audit will list broken links, missing titles and redirect chains in one report.
Write the numbers down. In a month, re-run the same three checks — that is how you prove the checklist worked.
1Let Google In: Crawlability
A page Googlebot cannot reach will never rank, no matter how good it is.
- Check the “discourage search engines” box is OFF. In WordPress, go to Settings → Reading and make sure “Discourage search engines from indexing this site” is unticked. This single checkbox is the most common reason a new or redesigned site vanishes from Google — developers tick it on staging sites and forget to untick it on launch.
- Check robots.txt. Visit yoursite.com/robots.txt. It should allow the important parts of your site and point to your sitemap. Never block `/wp-content/` or `/wp-includes/` — Google needs those files to render your pages properly. One misplaced `Disallow: /` blocks everything.
- Submit a clean XML sitemap. If you use Yoast SEO (this site does), your sitemap lives at yoursite.com/sitemap_index.xml. Submit it in Search Console → Sitemaps and check its status reads “Success”. A good sitemap contains only pages that return a 200 status and that you actually want indexed — no tag archives, no attachment pages, no admin pages.
- Use clean permalinks. Settings → Permalinks → “Post name” gives you short, readable URLs like yoursite.com/services/ instead of yoursite.com/?p=123. Never change the permalink structure of an established site without setting up 301 redirects from the old URLs, or you will break every existing ranking and backlink.
2Control What Gets Indexed
Being crawlable is not enough — you must also make sure Google indexes the right pages and ignores the junk.
- Noindex the low-value archives. Tag pages, date archives and author archives on a single-author site add almost nothing and dilute your site. In Yoast, go to SEO → Search Appearance → Archives and set tag, date and author archives to “no” for search engines.
- Set self-referencing canonical tags. Every page should point to itself as the canonical version, so Google does not split ranking signals between the www and non-www versions, or between a URL with and without a trailing slash. Yoast adds these automatically — check one page’s source code for
<link rel="canonical">to confirm. - Fix the Pages report. In Search Console, work through the “not indexed” reasons one by one. A page blocked by robots.txt or an accidental noindex is a five-minute fix. “Crawled but not indexed” usually means thin or duplicate content — that page needs real content or a noindex, not a resubmission.
- Kill duplicate content at the source. WordPress creates duplicates easily: category and tag pages showing the same posts, attachment pages for every image, and paginated archives. The fixes above (noindex archives, redirecting attachment pages to the image itself in Yoast’s Media settings) remove most of it.
3Speed and Core Web Vitals
Speed is a ranking signal, but for Pakistani visitors it matters even more as a business issue: most of your traffic arrives on mid-range Android phones over mobile data. A site that feels fast in Lahore on 4G is a site that converts.
Google’s thresholds are public and worth memorising:
| Metric | What it measures | Target |
|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content appears | Under 2.5 seconds |
| INP (Interaction to Next Paint) | How fast the page responds to taps and clicks (INP replaced FID in March 2024) | Under 200 milliseconds |
| CLS (Cumulative Layout Shift) | How much the layout jumps around while loading | Under 0.1 |
Practical fixes, in order of impact:
- Compress images before upload. Resize to the display size and convert to WebP where your theme supports it. A single uncompressed 3 MB banner photo can wreck an otherwise fast page. (This is also image SEO — alt text and file names matter for ranking too.)
- Use caching. A caching plugin (LiteSpeed Cache on LiteSpeed hosting, or WP Rocket) serves stored pages instead of rebuilding them on every visit. This alone often halves load time.
- Tame page builders. Elementor and similar builders add CSS and JavaScript on every page. Keep plugins lean, remove unused widgets and scripts, and avoid stacking three slider plugins when one will do.
- Use a CDN. Cloudflare’s free plan serves your static files from servers closer to your visitors, which helps international visitors and takes load off budget shared hosting.
- Check your hosting. If your server response time (TTFB) is over 600 ms, no plugin will save you. Budget shared hosting is the usual culprit — see our best web hosting guide for WordPress in Pakistan for what decent hosting actually costs.
4Mobile and Rendering
Google indexes the mobile version of your site first. Test on a real phone, not just by shrinking your laptop browser.
- Responsive design is non-negotiable. Buttons must be tappable, text readable without zooming, and no content wider than the screen. Test with PageSpeed Insights’ mobile view and fix what it flags.
- Make sure Google sees what visitors see. If important text or links only appear after JavaScript runs, check Search Console’s URL Inspection tool: it shows the HTML Google actually received. Key content, titles and canonicals must be in that HTML, not injected later by a script.
- HTTPS everywhere, with no mixed content. Your whole site must serve over HTTPS, not just the checkout. After migrating, hunt for mixed content — images or scripts still loading over http:// — which browsers flag and Google dislikes. One redirect rule (http → https, 301) should cover the entire site, and there should be exactly one version of your domain: either www or non-www, not both.
5Structured Data: Help Google Understand You
Structured data (schema markup) tells Google what your content is — an article, a business, a service, an FAQ — which qualifies you for richer search results.
- Yoast adds the basics automatically. Organization, WebSite, Article and Breadcrumb schema come out of the box. Make sure your organisation details (name, logo, social profiles) are filled in under SEO → Search Appearance → General.
- Add LocalBusiness schema if you serve a city. This is one of the highest-value additions for a Pakistani business, and it powers local results. (Our local SEO guide covers the Google Business Profile side of the same job.)
- Validate everything. Paste a page URL into Google’s Rich Results Test and fix any errors. Schema that does not match the visible page content is worse than no schema — Google treats it as misleading.
- Do not chase every schema type. Article, FAQ, Service and LocalBusiness cover almost every small business site. A broken Product schema on a page that sells nothing helps nobody.
6Security and Maintenance
An outdated WordPress site is a hacked WordPress site, and a hacked site loses rankings fast — Google will flag it in search results.
- Keep core, theme and plugins updated. Most WordPress hacks exploit known vulnerabilities in outdated software. Update promptly, but take a backup first — a bad update breaking your checkout is its own disaster.
- Delete what you do not use. Inactive themes and plugins are still attack surface. If you have not used a plugin in six months, delete it (not just deactivate it).
- Use a security plugin and limit login attempts. Wordfence or a similar plugin, plus two-factor authentication on admin accounts, stops the automated login attacks every WordPress site attracts daily.
- Check your PHP version. Ask your host for PHP 8.1 or newer. Old PHP is slower and unsupported, and some hosts still leave sites on versions that stopped receiving security fixes years ago.
7Internal Links and Site Structure
Links between your own pages tell Google which pages matter most — and they keep visitors moving through your site instead of bouncing.
- No page more than three clicks from the homepage. Pages buried deeper get crawled less often and rank worse. If a money page is five clicks deep, restructure your menus.
- No orphan pages. Every important page should be linked from at least one other page Google already knows. A new blog post with no internal links is nearly invisible.
- Use descriptive anchor text. Link with words that say what the page is about (“SEO pricing in Pakistan”), not “click here”. Every new post on this site links to 2–4 related guides for exactly this reason — see our SEO cost guide as an example of a page that benefits from it.
- Audit regularly. The same crawl tools from the baseline step will list orphan pages and pages with only one internal link. Fix the important ones first.
8Broken Links, Redirects and 404s
- Fix broken internal links. A link to a deleted page wastes crawl budget and frustrates visitors. Your crawl report lists them; fix or remove each one.
- Redirect moved pages with 301s, not 302s. A 301 tells Google the move is permanent and passes ranking signals; a 302 says temporary and does not. The Redirection plugin handles this without touching server files.
- Eliminate redirect chains. Page A → Page B → Page C slows crawling and leaks ranking signals. Point A directly at C.
- Build a useful 404 page. Some 404s are unavoidable (old external links, typos). A good 404 page explains the problem and links to your homepage, key services and search — it turns a dead end into a second chance.
9WordPress-Specific Traps
These are the issues generic SEO checklists miss, because they only exist on WordPress:
- Attachment pages indexed. By default, every image gets its own thin page. In Yoast → SEO → Search Appearance → Media, redirect attachment URLs to the attachment itself.
- Staging sites indexed. If your developer built the redesign on staging.yoursite.com and Google indexed it, you now compete with yourself. Password-protect staging sites and add noindex to them.
- Search results pages indexed. WordPress’s internal search creates a URL for every query (?s=keyword). These should never be indexed — Yoast blocks them by default, but verify.
- Category bloat. Twenty categories for thirty posts creates twenty thin archive pages. Keep categories few and meaningful; use tags sparingly or not at all.
- Plugin conflicts after updates. After any major update, spot-check your key pages: titles, schema and sitemap can all break silently when two SEO plugins fight, or when a caching plugin serves stale pages.
✓The Monthly Routine (15 Minutes)
You do not need the full audit every month. This short loop catches most regressions:
- Search Console → Pages report: any new indexing errors?
- PageSpeed Insights on the homepage: Core Web Vitals still passing?
- Crawl report: any new broken links or redirect chains?
- Updates: WordPress core, theme and plugins all current?
- One improvement: pick the single worst item from the full checklist and fix it this month.
Do that monthly, and the full checklist once or twice a year, and your site stays technically healthy while competitors slowly rot.
!Common Mistakes
- Installing three SEO plugins at once. Yoast and Rank Math (or any two SEO plugins) conflict — pick one and configure it properly.
- Obsessing over a PageSpeed score of 100. Field data (what real visitors experience) matters more than a lab score. A mobile score in the 80s with passing Core Web Vitals beats a 100 on desktop with a slow phone experience.
- Blocking Googlebot by accident. A robots.txt edit or a staging plugin left active can remove your whole site from search overnight. Check Search Console after every migration or redesign.
- Fixing content before fixing crawlability. Publishing ten new posts on a site Google cannot crawl is wasted effort. Technical health first, content second.
- Ignoring the Pages report for months. Indexing errors compound quietly. The businesses that rank are usually just the ones that noticed.
?Frequently Asked Questions
What is technical SEO in simple words?
Technical SEO is making sure search engines can find, crawl, understand and load your website properly. It covers site speed, mobile-friendliness, sitemaps, robots.txt, structured data, security and internal linking — everything except the words on the page and the links from other sites.
How often should I run a technical SEO audit?
A full audit once or twice a year, plus the 15-minute monthly routine in this guide. Run an extra audit after any redesign, migration, hosting change or major plugin update — that is when things break.
Can I do technical SEO myself, or do I need a developer?
Most of this checklist needs no code: Yoast settings, Search Console checks, image compression and plugin updates are all dashboard work. Server-level items (PHP version, redirect rules, hosting moves) are where a developer earns their fee — see our website cost guide for Pakistan for what that help typically costs.
What are good Core Web Vitals scores?
LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, measured on real visitors (field data in PageSpeed Insights or Search Console’s Core Web Vitals report), not just in lab tests.
Does technical SEO alone improve rankings?
It removes the ceilings on your rankings — a technically broken site cannot rank no matter how good its content is. But it does not replace content and links: think of it as the foundation, not the whole house. Content quality and backlinks still decide how high you go once the foundation is sound.
Why is my WordPress site slow even with a caching plugin?
Usually one of: slow shared hosting (high server response time), uncompressed images, a heavy page builder with too many plugins, or no CDN. Check them in that order — caching cannot fix a server that takes two seconds to answer.
Technical SEO is unglamorous work, and that is exactly why it pays off: most of your competitors will never do it. Work through this checklist once, keep up the monthly routine, and your content finally gets the rankings it deserves.

Get Your Site Technically Sound
At Azhad Niaz & Company in Peshawar, technical SEO audits are part of what we do every day — WordPress speed fixes, Search Console cleanups, schema setup and honest monthly reporting.