Technical crawl & index diagnosis
Review status codes, canonicals, robots, sitemaps, internal links and template patterns against observed search behaviour.
Technical SEO & website performance in Kolkata.
GreyBath helps Kolkata teams separate crawl, content and page-speed problems, then turn the evidence into a prioritised implementation backlog without ranking guarantees.
Explore the SEO and performance scope
01 / What we build
Diagnose first. Change what evidence supports.
Search architecture & content actions
Map useful page intent, duplication, gaps and internal links without turning keyword variants into thin landing pages.
Performance evidence & fix backlog
Combine lab and field signals with resource, template and hosting evidence, then verify completed changes.
City context, honestly stated
Supporting Kolkata teams without manufactured local signals.
We collaborate remotely with Kolkata teams using shared analytics, crawl exports and implementation reviews; GreyBath does not claim a Kolkata office.
Local relevance without doorway pages
Use service-area content only where it answers a distinct buyer need and avoid multiplying near-duplicate city pages.
English and Bengali follow audience evidence
Language expansion starts with query and customer needs, approved terminology and a plan for maintaining both versions.
Performance fixes respect the stack
Trace templates, assets, servers and third parties before recommending changes that could break editing or conversion paths.
02 / Where it fits
A search and speed pathway for sites with real operating constraints.
This work fits teams that can provide site access and implement fixes; an audit alone cannot improve search visibility or user experience.
Established service websites
Resolve indexation, internal-link and conversion-path issues without duplicating every service by city.
Product and catalogue sites
Control categories, filters, variants and product data so crawlers and buyers see consistent pages.
Content-led organisations
Improve templates, taxonomy and maintenance rules across growing article or resource libraries.
Sites after redesign or migration
Check redirects, canonical ownership, lost links and performance regressions against the previous URL set.
03 / How we work
Measure, isolate, implement and verify.
Establish a baseline
Record current crawl, index, traffic and performance evidence before recommending change.
Prioritise causes, not symptoms
Group issues by template and business impact, then assign actions, owners and dependencies.
Implement & recheck
Review completed changes, compare the agreed evidence and retain a backlog for unresolved constraints.
Define the site, market and access boundary.
Site size, platforms, markets, analytics history, access and implementation responsibility shape the proposal. Media, outreach and guaranteed rankings are not included by default.
Discuss your projectTechnical surface
Domains, subdomains, templates, rendering, hosting, scripts and third-party resources to inspect.
Search & content scope
Markets, languages, important journeys, existing pages and query evidence available for review.
Implementation ownership
Who can change code, content, infrastructure and measurement, plus the review cycle for verifying fixes.
Can you guarantee first-page rankings?
No. Search results depend on competition, authority, relevance, technical quality and changes outside GreyBath’s control. We can document and verify the work performed.
Do you need Search Console and analytics access?
Useful access improves diagnosis, but scope can begin with crawls and public responses. Any missing evidence is stated rather than guessed.
Will you create separate pages for every city?
Not by default. A location page must serve a distinct, truthful audience need. Near-duplicate city pages can create poor user value and search risk.
Can you improve Core Web Vitals?
We can diagnose and implement agreed fixes, then measure again. Results vary by templates, devices, traffic, hosting and third-party code, so a universal score is not promised.
Can the site target Bengali searches?
Yes, when query and customer evidence supports it and the business can maintain approved Bengali content. Automatic translation alone is not a search strategy.
A crawl or speed problem to resolve?