What technical SEO fixes, and what changes for you
Technical SEO is the layer under content and links, and the first thing I check in any of my SEO services. If Google cannot reach a page, renders it without its main content, indexes the wrong version of it, or measures it as slow on mobile, nothing written on that page matters. I audit those layers, rank the problems by how much traffic they are costing, and fix them, either directly on WordPress or through precise tickets for your developer. What changes for you is that the pages you have already paid to build start earning the traffic they should, and every later content investment lands on a site that can hold it.
Who this is for
- Sites where Search Console shows hundreds of “Crawled, currently not indexed” or “Duplicate without user-selected canonical” URLs and nobody knows why.
- Businesses that redesigned or migrated and lost traffic afterwards.
- eCommerce and listing sites with thousands of filter, sort and pagination URLs eating crawl budget.
- Sites built on React, Next.js, Vue or a page builder where the visible content is not in the HTML Google receives.
- Marketing teams abroad who need a senior technical audit and an implementation plan their agency or developer can execute.
If your problem is page-level content and titles rather than infrastructure, on-page SEO is the right page. If you want the full picture across technical, content and links before choosing, start with a complete SEO audit.
What a technical SEO engagement covers
Crawling and indexation
I crawl the site with Screaming Frog or Sitebulb, compare the crawl to the XML sitemap and to what Search Console reports as indexed, and reconcile the three lists. The gaps are where the problems are: orphan pages nobody links to, indexable URLs that should not exist, important pages returning soft 404s, redirect chains and loops from old migrations, and crawl budget spent on parameter URLs. Robots.txt gets reviewed line by line, because I regularly find rules written for a staging site still blocking CSS, image folders or entire sections in production.
Canonicals, duplicates and URL structure
Canonical tags are checked for every template, not just sampled, since one wrong rule in a theme header can point every product at the homepage. I resolve http and https, www and non-www, trailing-slash and uppercase variants, paginated series, and the duplicate paths that platforms like Shopify and WooCommerce create for the same product in several collections.
XML sitemaps and robots.txt
Sitemaps are rebuilt to contain only canonical, indexable, 200-status URLs with accurate lastmod dates, split by type on large sites, and submitted in Search Console. Non-indexable URLs are removed from them, because a sitemap full of noindexed or redirected pages tells Google the site is poorly maintained.
Structured data
Organization, LocalBusiness, Service, Product, Article, FAQ and BreadcrumbList markup is implemented or corrected, validated against Google’s rich result rules and monitored in Search Console. For larger schema projects there is a dedicated schema markup and structured data service.
Core Web Vitals and page speed
I work from field data (the Chrome UX Report in Search Console and PageSpeed Insights), not lab scores alone, and fix the causes: oversized images, render-blocking scripts, third-party chat and tracking tags, layout shifts from late-loading ads or fonts, and slow server responses on shared Nepali hosting. Deeper speed rebuilds are handled through the website speed and Core Web Vitals optimization service.
Internal linking
The crawl shows which pages carry link equity and which are buried four clicks deep. I restructure navigation, breadcrumbs, related-content modules and in-copy links so that commercial pages sit close to the homepage and every page in a silo is reachable and linked with descriptive anchors.
JavaScript rendering
For React, Next.js, Vue and Angular sites, I compare the raw HTML response with the rendered DOM to see what Google gets on first pass, check that titles, canonicals and links exist without JavaScript, and recommend server-side rendering, static generation or pre-rendering where content is missing. Page builders on WordPress get the same treatment when they inject content client-side.
Mobile, HTTPS and security
Mobile usability issues, mixed content after an SSL install, expired certificates, missing HSTS and hacked-site cloaking (still common on unmaintained WordPress installs in Nepal) are checked and fixed.
Hreflang and multi-region setups
For sites serving more than one country or language, hreflang and country targeting are audited as part of the technical work; the strategy side lives on the international SEO services page.
How I run a technical SEO audit
- Access and baseline. Search Console, GA4, hosting or CMS access. I export the index coverage report, the Core Web Vitals report and the current organic landing pages so that every later change can be measured against them.
- Full crawl. Desktop and mobile crawl with JavaScript rendering enabled, log file analysis when the host provides logs, and a separate crawl of the XML sitemap. On large sites I crawl by section to keep the analysis usable.
- Reconciliation. Crawled versus sitemap versus indexed versus receiving traffic. Each mismatch is classified: should be indexed and is not, is indexed and should not be, or is indexed but sending the wrong signals.
- Template-level review. One page of every template type is inspected by hand for canonical, meta robots, headings, structured data, rendered content and internal links. Fixing a template fixes every page that uses it.
- Prioritized findings. Each issue gets an impact rating (how many pages, how much traffic potential), an effort rating and an owner. The document reads as a work order, not a list of tool warnings.
- Implementation. On WordPress I make the changes myself. Elsewhere I write developer tickets with the exact URL patterns, expected behaviour and how to verify it, then test each deployment.
- Verification. Re-crawl, validate fixes in Search Console, request indexing of the priority URLs and monitor coverage and vitals for the following eight weeks.
A standard audit takes seven to ten working days. Large eCommerce or listing sites with tens of thousands of URLs take longer, and I say so after the first crawl rather than guessing before it.
Findings that come up most often
On Nepali sites
- Sites on shared hosting with server response times above one second, which makes every other speed fix a rounding error until hosting is addressed.
- Chandragiri Hills, before my work, loaded in more than six seconds and had no XML sitemap, no schema and broken internal links. Those were fixed first; the 180% organic traffic growth over six months came after.
- Page builders (Elementor, WPBakery) producing 3 to 5 MB pages and layout shift on every mobile load.
- Staging sites left indexable, or a robots.txt “Disallow: /” copied to production at launch.
- Duplicate Nepali and English versions of pages with no hreflang and no canonical, so Google picks one at random.
- Bank and enterprise sites where the security team blocks Googlebot by IP range or user agent without telling marketing.
On Australian, UK and US sites
- Headless or JavaScript-framework builds where the HTML response is an empty shell and product content only appears after client-side rendering.
- Faceted navigation on eCommerce sites generating millions of crawlable URLs, with crawl budget spent on colour and size filters while new products wait weeks to be indexed.
- Migrations where the agency redirected everything to the homepage or forgot the old image and PDF URLs that carried links.
- Third-party scripts (chat widgets, review badges, consent tools, tag managers with dozens of tags) accounting for most of the mobile load time.
- Hreflang sets pointing to redirected or noindexed URLs, so the country targeting quietly fails.
What you receive
- The technical audit document with prioritized findings, affected URL lists and fix specifications.
- Developer-ready tickets, or the fixes implemented directly on WordPress.
- A corrected XML sitemap and robots.txt, validated structured data and a Core Web Vitals before-and-after report.
- A monitoring setup in Search Console and a monthly check for regressions while the engagement runs.
Technical SEO is included in every monthly tier described on the SEO packages and pricing page, and available as a standalone audit and fix project. Sites about to change platform or design should read the website migration SEO page first, because preventing damage is cheaper than repairing it.
Next step
Request a free technical SEO check and I will run a first crawl, look at your Search Console coverage and reply with the issues that are costing you the most traffic. For a full engagement, see all SEO services or contact me with the site URL.