# Technical SEO & Core Web Vitals: The Complete 2026 Guide for Business Owners
Your website could have the best content in Mumbai for your industry. It could be beautifully designed, perfectly written, and accurately priced. And Google might still not rank it because the technical foundation is broken.
Technical SEO is the layer of search optimisation that most business owners never see and most SEO agencies underexplain. It is not about keywords. It is about whether Google can find your pages, understand them, load them fast enough to show them to users, and trust them enough to rank them. Get the technical layer wrong and everything else your content, your backlinks, your Google Ads delivers less than it should.
In this guide you will learn what technical SEO actually covers, why Core Web Vitals matter to your ranking and your customers, how to identify the most common technical issues on a Mumbai website, what a proper technical audit costs, and the fixes that make the biggest difference for real businesses. As the founder of Perceptra where we manage a 3,870-page static site across 43 services and 90 Mumbai locations I will tell you what the technical problems look like in practice and how we fix them.
What is technical SEO and what does it actually cover?
The distinction that matters: content SEO tells Google what your pages are about. Technical SEO tells Google that your pages exist, are accessible, load fast enough to be worth showing, and are structured correctly to be understood. Both are necessary. Technical SEO comes first because content optimisation built on a broken technical foundation is wasted effort.
The seven technical SEO categories
1. Crawlability and indexability Can Google find and process your pages? Issues here include blocked pages in robots.txt, noindex tags on pages that should rank, broken internal links preventing Googlebot from discovering content, and orphaned pages with no links pointing to them.
2. Site speed and Core Web Vitals How fast does your site load for real users on real devices? Google uses Core Web Vitals Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP) as ranking signals. A slow site loses both rankings and customers.
3. Mobile-first indexability Google primarily uses the mobile version of your site for indexing and ranking. A site that looks perfect on desktop but has a broken mobile experience will underperform even for desktop searches.
4. HTTPS and security An HTTP site (not HTTPS) is flagged as "not secure" in Chrome and treated as a trust risk by Google. All pages must serve over HTTPS with a valid SSL certificate.
5. Site architecture and URL structure How your pages are organised and linked affects how efficiently Google crawls your site and how link authority flows between pages. A flat, logical structure with clean URLs is better for both Google and users.
6. Schema markup (structured data) Machine-readable code that helps Google understand what your pages are about beyond their text content business hours, reviews, products, FAQs, events. Schema markup enables rich results in Google search.
7. Duplicate content and canonicalisation Multiple URLs serving the same or very similar content confuse Google and dilute ranking signals. Canonical tags tell Google which version of a page is the one that should rank.
What are Core Web Vitals and why do they matter in 2026?
Since their introduction as a ranking factor, Core Web Vitals have become the most quantifiable technical SEO requirement. Unlike many ranking factors that are directional and hard to measure, CWV gives you exact scores and specific thresholds that separate "good," "needs improvement," and "poor."
The three Core Web Vitals explained
| Metric | What it measures | Good threshold | Poor threshold |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How long until the main content is visible | Under 2.5 seconds | Above 4 seconds |
| INP (Interaction to Next Paint) | How quickly the page responds to user input | Under 200ms | Above 500ms |
| CLS (Cumulative Layout Shift) | How much content shifts unexpectedly during load | Under 0.1 | Above 0.25 |
Why LCP is the most impactful for Mumbai websites
LCP the time until your main content appears is the metric that most directly affects user experience and abandonment. A page that takes 4+ seconds to show its main content will lose a significant percentage of visitors before they see your offer, your pricing, or your contact number.
For Mumbai businesses with image-heavy websites (real estate galleries, restaurant menus, clinic team photos, e-commerce product listings), LCP is almost always the problem. The typical culprits: uncompressed hero images served at desktop resolution to mobile devices, images that are lazy-loaded when they should load eagerly, or fonts that block rendering.
On the Perceptra static site 3,870 pages across 43 services and 90 Mumbai locations the single highest-impact technical fix was converting uncompressed JPG hero images to WebP format and setting loading="eager" on the LCP image. LCP dropped from an average of 3.8 seconds to 1.9 seconds across the site, moving pages from "needs improvement" to "good" status in PageSpeed Insights.
How to check your Core Web Vitals
Google provides two data sources:
- PageSpeed Insights (pagespeed.web.dev): Combines lab data (simulated) and field data (real user measurements). Field data is what Google uses for rankings. Lab data is diagnostic.
- Google Search Console ? Core Web Vitals report: Shows which URLs are in "good," "needs improvement," or "poor" status based on real user data.
Check both. Lab data tells you what to fix. Field data tells you whether the fix actually helped real users.
Ready to take the next step?
Let Perceptra scope the right approach for your business.
Book a Free Strategy Session ?The five technical issues that silently kill most Mumbai websites
These five issues appear in virtually every technical SEO audit we run for Mumbai businesses. Some are configuration mistakes made during website setup that were never noticed. Others are drift things that broke gradually over time. All five are fixable.
Issue 1: Unoptimised images destroying page speed
The most common technical issue on Indian business websites. A hero image photographed on a DSLR camera, uploaded at original resolution (4MB+), and served to mobile users on a 4G connection is a page speed disaster.
Diagnosis: Run PageSpeed Insights on your homepage. If LCP is above 2.5 seconds, look at "Opportunities" an unoptimised hero image will appear there.
Fix: Convert images to WebP format (40 60% smaller than JPG at equivalent quality). Set the correct width and height attributes to prevent CLS. Use loading="eager" on the LCP image (usually the hero). Use loading="lazy" on all below-the-fold images. For large sites, use a CDN.
Full guide: image optimisation for faster pages.
Issue 2: Canonical tag errors creating duplicate content
A website with multiple URLs serving essentially the same content www vs non-www, HTTP vs HTTPS, trailing slash vs no trailing slash, paginated versions without canonicals is splitting its ranking signals across multiple URLs instead of concentrating them on one.
Diagnosis: Check your canonical tags by viewing page source and searching for . Does it point to the correct, authoritative URL? Run a site crawl with Screaming Frog or Sitebulb to identify pages with missing, self-referencing, or incorrect canonicals.
Fix: Ensure every page has a canonical tag pointing to the preferred URL. For paginated pages, use rel="next" and rel="prev" or canonical to the first page. Ensure your CMS is not generating duplicate URLs for the same content.
Full guide: canonical tags and duplicate content fixes.
Issue 3: Pages accidentally blocked from Google
A single line in robots.txt can block Google from crawling your entire website. A noindex tag on a category page can hide dozens of product pages from Google's index. These mistakes are surprisingly common often introduced during development and never removed.
Diagnosis: Check yourdomain.com/robots.txt and confirm it is not blocking important sections of your site. In Google Search Console, check the Coverage report for "Excluded" pages look for "Crawled currently not indexed," "Excluded by robots.txt," and "noindex tag" reasons.
Fix: Remove Disallow: / or other broad blocking rules from robots.txt on live sites. Remove noindex tags from pages that should rank. For staging environments, use password protection rather than robots.txt blocking.
Full guide: fixing the noindex tag that hides your site.
Issue 4: Broken internal links creating crawl dead-ends
Every broken internal link is a dead end for Googlebot. On large sites 100+ pages broken internal links are common, often created when pages are deleted or URLs are changed without redirect updates.
Diagnosis: Run your site through Screaming Frog (free up to 500 URLs). Filter by HTTP status 404. Every 404 you find as an internal link is a crawl dead-end.
Fix: For deleted pages with historical traffic or backlinks: add a 301 redirect to the most relevant live page. For pages moved to a new URL: 301 redirect the old URL to the new one. For internal links pointing to wrong URLs: update the links in the site's navigation or content.
Full guide: redirects done right during a site revamp.
Issue 5: Missing schema markup
Schema markup is machine-readable JSON-LD code in your page's
Diagnosis: Test your pages with Google's Rich Results Test (search.google.com/test/rich-results). If you have FAQs on your page but no FAQPage schema, you are missing potential FAQ rich results. If you have a physical business but no LocalBusiness schema, you are missing NAP (Name, Address, Phone) structured data.
Fix: Add the relevant JSON-LD schema to each page type. For service businesses: LocalBusiness + Service schema. For blog posts: Article/BlogPosting + BreadcrumbList schema. For FAQ sections: FAQPage schema. For service pages with prices: Service + Offer schema.
The full structured data guide is in structured data basics every site needs.
How to do a technical SEO audit: the right approach
A technical SEO audit is a systematic review of your website's technical infrastructure to identify issues preventing search engines from crawling, indexing, and ranking your pages effectively. A proper audit covers crawlability, indexability, speed, mobile usability, security, architecture, and structured data producing a prioritised list of fixes sorted by impact.
The word "audit" is used loosely by SEO agencies. A real technical audit is not a Semrush export with 200 flags and no explanation. It is a structured analysis with prioritised findings, specific fix instructions, and estimated impact for each issue.
The seven-section technical audit
Section 1: Crawl analysis Use Screaming Frog to crawl your full site. Identify: broken links (404s), redirect chains (301 ? 301 ? 301), pages blocked by robots.txt, pages with noindex tags, pages with missing titles or meta descriptions, and pages with duplicate content.
Section 2: Indexability review Check Google Search Console Coverage report. Understand which pages are indexed, which are excluded and why, and which are submitted in the sitemap but not indexed. Cross-reference with your expected page count.
Section 3: Core Web Vitals assessment Pull CWV data from Google Search Console (field data) and PageSpeed Insights (lab data) for your key page types: homepage, service pages, product pages, blog posts. Identify which page types fail LCP, INP, or CLS thresholds.
Section 4: Mobile usability Check Google Search Console's Mobile Usability report. Test your site manually on an actual mobile phone, not a browser resize. Look for: text too small to read, clickable elements too close together, content wider than the screen.
Section 5: HTTPS and security Confirm your site serves entirely on HTTPS. Check for mixed content (HTTP resources loaded on an HTTPS page) using your browser's developer console. Verify your SSL certificate is valid and not expiring within 30 days.
Section 6: Architecture and internal linking Map your site's internal linking structure. Do your most important pages have the most internal links pointing to them? Are there orphaned pages with no internal links? Do your URL structures reflect your content hierarchy?
Section 7: Schema markup review Test five representative pages with Google's Rich Results Test. Identify which schema types are present, which are erroring, and which are missing for the content on each page type.
What technical SEO costs in Mumbai (2026)
Technical SEO audit cost in Mumbai in 2026 depends on website size, platform complexity, and the depth of reporting required. A basic audit for a 20-page brochure site starts from a lower project fee. A comprehensive audit for a 500+ page e-commerce or multi-location site with fix recommendations and implementation support starts from a higher scoped fee.
The most important distinction: an audit that generates a report is different from an audit that generates fixed pages. Some agencies charge for the finding. Some charge for the finding and the fix. At Perceptra, we audit, report, and implement one project, one written quote.
The three audit tiers
Audit type Best for Covers Starting from Snapshot audit 10 50 page sites, first-time SEO Core vitals, crawl errors, indexability, schema gaps Lower project fee Full technical audit 50 500 page sites All 7 sections, prioritised fix list, implementation guide Mid project fee Enterprise audit 500+ pages, e-commerce, multi-location Full audit + fix implementation + 30-day monitoring Larger project fee
What the Perceptra site audit found
When we conducted a technical audit of the Perceptra static website, it scored 41/100 on initial assessment. The specific findings: broken JSON-LD schema on all pages, incorrect canonical tags pointing to the wrong protocol variant, no robots.txt or sitemap, missing alt text on 80%+ of images, and 13 orphaned pages with no internal links.
Every one of these issues was fixable. The audit identified them; the implementation fixed them. That is what a proper technical audit delivers not just a score, but a roadmap.
Book a free scoping session
Technical SEO for large sites: the specific challenges
Technical SEO for large websites 500+ pages introduces problems that small sites never encounter: crawl budget exhaustion, template-generated duplicate content, redirect chain accumulation, and schema implementation at scale. Each requires a systems approach rather than page-by-page fixes.
The Perceptra website 3,870 pages across 43 service 90 location combinations gives us direct experience with large-site technical SEO that most Mumbai agencies do not have. Here is what we learned.
Crawl budget
Crawl budget is the number of pages Googlebot will crawl on your site in a given timeframe. For small sites (under 500 pages), crawl budget is rarely a constraint. For large sites, it determines whether new or updated pages are discovered and indexed promptly or wait weeks.
Managing crawl budget on the Perceptra site required: blocking non-essential URL parameters (filter combinations that created thousands of low-value URL variants), ensuring the sitemap contained only canonical, indexable URLs, and improving page speed so Googlebot could crawl more pages per session.
Full guide: why crawl budget matters on big sites.
Template-generated duplicate content
Location-based service pages "web design services in Andheri," "web design services in Bandra" share structural and content similarities. Without careful differentiation, Google may treat them as near-duplicates and index only one or a few, ignoring the others.
The fix: ensure each location page has genuinely unique content local case studies, area-specific details, location-specific FAQs, and locally relevant internal links in addition to the core service description. Thin location pages rank poorly; substantive location pages rank well.
Full guide: technical SEO for large location-page sites.
Redirect management at scale
On a site that has undergone multiple redesigns or URL structure changes, redirect chains accumulate. A page that has been moved three times may redirect through three intermediate URLs before reaching the destination. Each hop in a chain dilutes the link equity passed and slows crawling.
Audit all redirects quarterly on large sites. Flatten chains: redirect old URLs directly to the final destination, removing intermediate steps.
How to prioritise technical SEO fixes
Technical SEO fixes should be prioritised by three criteria: whether the issue prevents pages from being indexed at all (fix immediately), whether it directly reduces ranking potential for high-value pages (fix in week 1 2), or whether it improves incrementally once the foundation is sound (fix in month 1 3). Not all technical issues are equally urgent.
Tier 1: Critical (fix immediately)
- Pages blocked by robots.txt that should rank
- Noindex tags on important pages
- Site not on HTTPS
- Canonical tags pointing to the wrong page
- Sitemap containing non-indexable URLs
These issues actively prevent pages from ranking. Fix before any other SEO work.
Tier 2: High impact (fix within 2 weeks)
- LCP above 4 seconds on key pages
- Broken internal links on high-traffic pages
- Missing or erroring schema on commercial pages
- Mobile usability failures on core pages
- 404 pages with significant backlinks (need 301 redirect)
These issues are reducing ranking and conversion for your most important pages. Fix promptly.
Tier 3: Progressive improvement (fix within 3 months)
- LCP between 2.5 4 seconds (move to "good" from "needs improvement")
- Missing schema on secondary pages
- Internal linking optimisation for deeper pages
- Image optimisation on older content
- Crawl budget optimisation for large sites
These are real improvements but not emergencies. Address systematically after Tier 1 and 2 are resolved.
Technical SEO vs content SEO: how they work together
Technical SEO sets the floor the minimum performance level your content can achieve in Google's rankings regardless of quality. Content SEO sets the ceiling the maximum relevance and authority you can build for specific topics. Both are necessary, but technical issues suppress the ceiling that content can reach.
A website with excellent content but poor technical SEO is like a well-stocked store in a building with a broken address sign and a narrow, unpaved road leading to it. The stock (content) is great. The infrastructure (technical SEO) prevents customers from finding it.
In practice: we have seen Mumbai service businesses with detailed, genuinely useful service pages ranking on page 5 for their target keywords. After a technical audit and basic fixes correct canonicals, sitemap submission, LCP improvement, schema addition the same content, unchanged, moved to page 2 or 3. The content was already good enough. The technical layer was suppressing it.
This is the reason technical SEO comes before content SEO in any serious organic growth programme. Fix the floor. Then build the ceiling.
See SEO Strategy, Content & Keyword Foundations for the content layer that sits on top of the technical foundation.
A note from building technical SEO for 3,870 pages
Here is what three years of technical SEO work on large Indian websites taught me: the most expensive technical SEO mistakes are the ones made at launch.
A website that launches with incorrect canonical tags, no sitemap, blocking robots.txt directives, and unoptimised images starts from a deficit that takes months to recover from. The same work done correctly at launch costs nothing extra it is a configuration choice, not a rebuild.
The practical implication: if you are building or rebuilding a website, invest in a technical SEO review before the site goes live. It is far cheaper than fixing a broken foundation after launch. See technical SEO checklist before launch for the exact pre-launch checklist we use.
"Technical SEO is not glamorous. It is robots.txt files and image attributes and canonical tags. But it is the difference between a website that works and a website that looks like it should work." Aamir Khan, Founder, Perceptra
Final thoughts
Technical SEO in 2026 is not optional for any Mumbai business that depends on Google for leads, traffic, or customers. Core Web Vitals are a ranking signal. Mobile-first indexing is the standard. Schema markup is how Google understands what you do. Crawlability is how Google knows you exist.
The good news: most technical SEO issues are fixable. They are not algorithmic problems or competitive problems they are configuration problems. An audit identifies them. An implementation plan fixes them. A monitoring process keeps them fixed.
Ready to find out what technical issues are holding your site back? Book a free 30-minute technical SEO review with Perceptra. We run through your key pages, check Core Web Vitals, identify the most impactful issues, and give you an honest assessment of what fixing them involves.
Book a Free Technical SEO Review ?
Aamir Khan is the Founder of Perceptra, a Mumbai digital growth studio that builds technical SEO infrastructure, manages large-scale location page sites, and audits websites across industries. He has worked on sites ranging from 10-page brochure sites to the 3,870-page Perceptra site and writes plainly about what the technical layer actually involves. View full author profile ?
Frequently asked questions
`html