DMDigital MansoorAI SEO Consultant

Technical SEO consultant, Ahmedabad

#1 Technical SEO Consultant: Make Your Site Easy to Crawl, Index and Use

Technical SEO is the plumbing. If search engines cannot reach a page, render it or tell which version to index, nothing you write on it matters. I audit the site, rank the faults by business impact and fix the ones that move traffic, with developer ready tickets where code changes are needed.

Get a free first lookSee the plan

Mansoor Bhanpurawala. SEO since 2012, 14+ years, 600+ projects. Based in Ahmedabad.

01CrawlBots can reach every page that matters
02IndexThe right version of each page is stored
03ServePages load fast and work on phones

Scope

What technical SEO covers

Think of four stages. A search engine has to find a URL, fetch it, render it and decide whether to store it. Then it serves the stored page to a searcher on a real device. A fault at any stage can hide a good page, and the fix at each stage is different.

Discovery

Internal links, sitemaps, redirects and external links that lead crawlers to your pages.

Crawling

Robots.txt, server responses, crawl traps and parameter URLs that waste crawl time.

Rendering

JavaScript, lazy loaded content and blocked resources that hide text from search engines.

Experience

Speed, layout stability, mobile usability and security on real devices.

Core Web Vitals

The speed numbers I check

Google measures three Core Web Vitals on real visits, at the 75th percentile. The published good thresholds are below. They have not changed, despite rumours that Google tightened the loading threshold.

MetricMeasuresGoodPoor
LCPHow fast the largest visible element loads2.5 seconds or lessOver 4 seconds
INPHow fast the page responds to taps and clicks200 milliseconds or lessOver 500 milliseconds
CLSHow much the layout jumps while loading0.1 or lessOver 0.25

I look at field data first, from Search Console and the Chrome User Experience Report, because those are real visits. Lab tests such as Lighthouse help diagnose causes but do not replace field data. Speed is one signal among many, so I fix the metrics that real users fail, not the ones a score tool dislikes.

Crawling

Crawl and robots.txt

I read your server logs where available, or the Search Console crawl stats where not, to see what bots actually request. I check robots.txt for rules that block important sections, scripts or styles. I also look for crawl traps: calendar pages, filter combinations, session parameters and internal search results that create endless URLs.

I handle bots by purpose. Search crawlers should reach everything you want ranked. Other bots, including AI crawlers, each have their own controls, and blocking one does not block another. I align those choices with your business goals instead of copying a template.

Indexing

Indexing and canonicals

What I fix

  • Important pages marked noindex by mistake
  • Duplicate URLs without a clear canonical
  • Soft 404 pages and thin placeholder pages
  • Parameter and tag pages that bloat the index
  • Pages in the sitemap that redirect or return errors

What I leave alone

  • Pages Google chose not to index because they add nothing
  • Old URLs that redirect correctly
  • Small, useful utility pages with a clear purpose
  • Anything where "not indexed" is the right result

The Page Indexing report in Search Console lists reasons for non-indexed URLs. Many are normal. I separate the ones that cost you visits from the ones that do not.

Rendering

JavaScript and rendering

If content appears only after scripts run, search engines can still miss it or index it late. I compare the raw HTML with the rendered page, check that internal links are real links with URLs and test that key text, headings and canonical tags exist in the initial response where possible. On sites built with page builders, I look for heavy scripts, hidden duplicate content for mobile and desktop and lazy loading that stops images from being found.

Site structure

Architecture and internal links

A page that no other page links to is hard to find. A page buried six clicks deep gets less attention from crawlers and users. I map the site, check depth, find orphan pages and rebuild navigation and internal links so important pages sit close to the homepage and related pages support each other.

I also check URL patterns. Short, readable, stable URLs are easier to maintain. I only recommend changing URLs when there is a clear gain, because every change needs redirects and carries risk.

Migrations

Redirects, migrations and relaunches

Step 1

Inventory

List every live URL, its traffic, links and purpose before any change.

Step 2

Map

Match each old URL to its closest new URL. Merge or retire the rest with a stated reason.

Step 3

Stage and test

Check redirects, canonicals, robots rules, sitemaps and tracking on a staging copy.

Step 4

Launch

Switch, submit the new sitemap and watch Search Console and server logs for errors.

Step 5

Review

Compare traffic and indexing at 2, 6 and 12 weeks and fix gaps.

Most traffic losses after a redesign come from missing redirects and changed templates, not from Google punishing a new design. A planned migration avoids them.

Structured data

Structured data that matches the page

I add markup only where it describes content visible on the page: organisation, product, article, breadcrumb and similar. I validate it with Google's tools. Markup that claims reviews, prices or facts the page does not show is a risk, not a benefit. Some rich result types have been restricted or retired over time, so I check current Google documentation before recommending any type.

WordPress and builders

Common faults on WordPress and page builder sites

01

Plugin overload

Several plugins loading the same scripts on every page. I remove or defer what a page does not use.

02

Heavy builder markup

Deeply nested containers and unused widgets slow rendering. I trim templates before touching content.

03

Image weight

Original camera files uploaded and scaled by CSS. I resize, compress and set dimensions.

04

Duplicate archives

Tag, author and date archives indexed with thin content. I noindex the ones with no value.

Deliverables

What you receive

You get a prioritised audit in plain language, a ticket for each fix with the exact change, the reason and how to test it, and a before and after view in Search Console. I mark each item as high, medium or low by expected impact and effort. I do not hand over a 200 page export from a crawler. I work with your developer, host or plugin vendor directly, and I check the fix on the live site after release.

Fit

Who needs this

It fits sites with unexplained traffic drops, pages that are not indexed, slow mobile performance, a recent redesign, a planned migration or a large catalogue. It also fits sites that have never had a technical review. It does not fit a small brochure site with fewer than 20 pages and no problems, where an hour of checks is enough, and I will tell you that on the first call.

Prioritising

How I decide what to fix first

A crawler can report thousands of issues, and most do not matter. I score each fault on three questions: how many pages it touches, how much traffic or revenue those pages carry and how hard the fix is. A broken canonical on your top service page beats a thousand missing alt attributes on old blog images.

Fix first

  • Important pages blocked or not indexed
  • Redirect chains and loops on high traffic URLs
  • Templates that fail Core Web Vitals for most visitors
  • Duplicate versions of money pages

Fix later or skip

  • Warnings that tools flag but Google ignores
  • Title length complaints on pages that already rank
  • Minor markup validation notes
  • Issues on pages with no traffic or purpose

Worked example

A typical finding and fix

A services site has 40 pages in the sitemap but only 22 indexed. Search Console shows "Discovered, currently not indexed" for the rest. A check shows that 14 of them are orphan pages with no internal links, and four are near duplicates of other pages.

The fix is plain: link the useful orphan pages from related pages, merge the four duplicates into stronger pages with redirects, and remove the weak pages from the sitemap. Nothing needs a plugin or a rebuild. Within a few weeks the indexed count follows the sitemap, and the pages that matter finally have a chance to rank.

First 30 days

What the first month looks like

Days 1 to 5: access and crawl

Search Console and analytics access, a full crawl, server log review where available.

Days 6 to 15: audit

Findings grouped by stage, with impact and effort for each fix.

Days 16 to 25: tickets and fixes

Developer ready tickets for each item, plus the changes I can make directly.

Days 26 to 30: retest

Recrawl, check the live fixes and record the baseline for the next review.

Tools

The tools behind the audit

I combine a site crawler, Search Console, the Chrome User Experience Report, PageSpeed Insights, your analytics and server logs where I can get them. Each tool has blind spots. A crawler sees your site as a bot with no history, Search Console shows what Google chose to report and lab speed tests run on one device and one connection.

When two sources disagree, I trust the one that reflects real behaviour: Search Console and field data over lab scores. I also test fixes on the live site before I call them done, because a ticket marked complete does not always match what is running in production.

What is technical SEO?

It is the work that lets search engines find, crawl, render, index and serve your pages, along with speed, mobile usability and security.

What are the Core Web Vitals thresholds?

Good is LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, measured at the 75th percentile of real visits.

Does page speed affect rankings?

It is one signal among many. A slow site hurts users more directly, so I fix the metrics real users fail.

Why is my page not indexed?

Common reasons are noindex tags, duplicate content, thin content, crawl blocks or Google judging the page as low value. Search Console shows the stated reason.

Do I need an XML sitemap?

It helps search engines discover pages, especially on large sites. It should list only canonical, indexable URLs.

Is JavaScript bad for SEO?

Not always, but content that appears only after scripts run can be missed or indexed late. I test the rendered page against the raw HTML.

How do you handle a site migration?

Inventory, redirect map, staging tests, launch checks and follow up reviews at 2, 6 and 12 weeks.

Do you fix the issues or only report them?

I write developer ready tickets and work with your team. Where you have a plugin or CMS setting, I can make the change with your approval.

Should I block AI crawlers?

It depends on whether you want to appear in AI search. Each crawler has its own control, so I set rules per bot against your goals.

How long does a technical audit take?

A focused audit usually takes one to two weeks. Large sites need longer.

Will fixes bring immediate traffic?

Some do, such as unblocking indexable pages. Others compound slowly. I report what moved and what did not.

How do we start?

Send your site and your Search Console access if you can. I run a first check and show the top issues.

Get a technical check of your site

Send your site and Search Console access. I will show the top issues and what they cost you.