Executive summary
Where Zeway is today
Zeway is not losing because it has no SEO footprint. It is losing because a small footprint is spread across thin or overlapping charging pages, legacy blog URLs and a JavaScript-dependent delivery layer while competitors capture much broader commercial architecture, brand demand and third-party authority.
- Coverage: Bolt exposes a deep charger, solution, industry, franchise, app, calculator and service architecture.
- Transactionality: Yulu and Eveez connect rental searches to plans, products, app or partner actions.
- Depth: the public crawl found a median 1,819 words across sampled Kazam pages and 1,894 across Bolt, versus 290 across rendered Zeway routes.
- Authority: the baseline shows Yulu at 2,200 referring domains and Bolt at 1,400 versus Zeway’s 133.
- Brand/entity strength: Yulu’s baseline 307 AI mentions contrasts with Zeway’s one.
Own two connected demand systems.
Rental: city availability, plans, delivery and fleet use cases, price factors, documents and booking.
Charging: site assessment, RWA, workplace, campus, hospital, retail, fleet, installation and infrastructure.
Use guides, comparisons, original data and PR to move authority into those commercial hubs.
The 10 biggest gaps
The 10 biggest opportunities
Research integrity
Three evidence layers, never mixed
Screenshot benchmark
Approx. 31 Aug 2026, Semrush India, six months. User-provided and not independently verified.
Current public crawl
01 Sep 2026. Headers, robots, sitemaps, rendered pages, metadata, schema, links and public suggestions.
Derived strategy
Scores, priorities, forecasts and revenue scenarios calculated from labeled inputs and assumptions.
Executive competitive scorecard
The gap is structural, not marginal
| Domain | AS | Traffic | Keywords | Ref. domains | Backlinks | AI mentions | Commercial | Transactional |
|---|---|---|---|---|---|---|---|---|
| Zeway | 17 | 123 | 84 | 133 | 1.1K | 1 | 44.6% | 4.6% |
| Kazam | 26 | 2.6K | 489 | 450 | 3.6K | 141 | 22.7% | 6.9% |
| Bolt.Earth | 40 | 74.3K | 3.4K | 1.4K | 7.2K | 160 | 37.2% | 11.7% |
| Yulu | 45 | 138.6K | 1.4K | 2.2K | 65K | 307 | 10.5% | 34.6% |
| Eveez | 27 | 5.3K | 224 | 190 | 318 | 13 | 40.5% | 20.9% |
All values in this table are the user-provided screenshot baseline. Top 3/10/20/50/100 ranking counts were not available and were not fabricated.
SEO performance index
Zeway scores 9.5 / 100 on the comparable-data proxy
Traffic gap diagnosis
Sixteen compounding causes
Keyword coverage
84 baseline keywords versus Bolt’s 3,400.
Intent coverage
Only 4.6% transactional versus Yulu’s 34.6%.
Content depth
Median 290 rendered words across Zeway crawl versus 1,819 Kazam sample and 1,894 Bolt.
Commercial pages
Broad charging URLs exist, but plan, proof and decision support are thin.
Transactional pages
Weak pricing, booking, quote and availability architecture.
Local SEO
Only Kanpur/Lucknow dedicated service content observed.
Programmatic SEO
No safe, data-backed local template system yet.
Internal linking
Broken relative links and duplicate route conventions waste paths.
Backlinks
133 baseline referring domains versus Yulu’s 2,200.
Brand search
Yulu’s navigational share and brand ecosystem are materially stronger.
Authority
Authority Score 17 versus Yulu 45 and Bolt 40.
Architecture
Competitors expose cleaner product, solution and partner hierarchies.
Location pages
No verified multi-city hub or service-area framework.
Topical authority
Charging content is broad but fragmented; rental and B2B clusters are shallow.
SERP features
FAQ, local pack, snippets and video require page-level query design.
AI visibility
One baseline mention, soft-404 llms.txt and limited third-party entity evidence.
Keyword and intent strategy
Commercial demand first
Capture immediate mobility demand
Electric scooter rental, monthly rental, subscription, near me, price, delivery rider, documents and city availability.
Open 180-keyword shortlist →Capture site and fleet decisions
RWA, workplace, office, university, fleet, delivery hub, charging installation, provider, franchise and infrastructure.
Open Top 100 →Search volume, KD, CPC and ranks are explicitly unverified in every row. Priority uses live suggestion frequency, intent, modeled business value, long-tail feasibility and observed page gap.
Content and competitor page gap
Build a commercial operating system, not a blog factory
1,533 sitemap URLs
Massive informational coverage and long-form publishing. Learn the topical breadth; do not copy dated, repetitive blog volume.
233 sitemap URLs
Best solution/product taxonomy: RWA, workplace, enterprise, fleet, OEM, franchise, services, calculator and charger catalogue.
Product + partner engine
Strong brand, products, business partnership, app, news, testimonials and transactional ecosystem.
Rental clarity
Simple subscription/rental positioning and franchise action despite material technical weaknesses.
Local and programmatic SEO
Service truth before city scale
Safe programmatic pilot
Start with one reusable city component, but publish only two validated city hubs. Require unique operations, plans, pickup/coverage, support, proof, FAQs and lead routing.
Unsafe scale
Do not generate “near [area]” pages from keyword permutations. Without live vehicle/station inventory, coordinates, service boundaries or installations, those pages are doorway-like duplicates.
Technical SEO audit
Fix what blocks every future page
Pre-render or server-render main content
All 120 sitemap URLs returned metadata and schema but no main body/H1 in the initial HTML crawl. Search systems can render JavaScript, but relying on that adds latency and leaves non-JS agents/social systems without page content.
Repair malformed relative links
Live rendered discovery produced internal error paths such as /www.facebook.com/zeway.in/ and nested social URLs. Fix hrefs, redirect known malformed paths and add link CI.
Fix missing H1 and thin rendered routes
15 rendered HTTP-200 URLs lacked an H1. 69 rendered variants were below 300 words; 120 canonical sitemap pages need consolidation and intent-level review rather than automatic expansion.
Repair duplicate blog pagination
The blog and /page/2–4 variants rendered the same hub content. Serve real paginated sets or consolidate to a crawlable archive.
Return a real llms.txt or a real 404
Zeway’s /llms.txt and /pricing.md return the 9,620-byte SPA shell as HTTP 200. Bolt publishes a valid plain-text llms.txt that exposes its commercial architecture.
Architecture, on-page and internal links
Every money page needs a clear job
On-page contract
- One query-aligned H1
- Answer in first 60 words
- Availability and pricing factors
- Named proof and limitations
- Visible CTA above and after proof
- FAQ from sales objections
Internal link contract
- 5–20 relevant links per money page
- Spoke → pillar → commercial page
- Descriptive anchors, not “learn more”
- Navigation links for core services
- Case study → service + location
- No orphan revenue URLs
Schema contract
- Organization identity consistency
- Service where service is visible
- BreadcrumbList for hierarchy
- Article + named author/reviewer
- FAQ only for visible FAQs
- No self-serving review markup
Commercial conversion and revenue
Keyword → page → CTA → lead → revenue
Product catalogue, set-up flow, plan selection, app, franchise, distributor, calculator and use-case-specific sales pages.
App download, product clarity, partner economics, testimonials, media authority and ride/partner actions.
Deep education around charging, software/hardware and wide informational capture.
Simple rental proposition, subscription plans and franchise/rental actions despite weaker technical SEO.
Illustrative revenue model per 1,000 organic visitors
Execution plan
90 days to a working revenue foundation
Truth + foundation
- Export GSC, GA4, CRM, GBP and link/rank tools
- Validate services, territories and revenue actions
- Fix malformed links and URL convention
- Scope SSR/pre-rendering
- Brief rental and charging pillars
- Implement CRM attribution spec
Ship money pages
- Deploy SSR priority templates
- Publish rental and charging pillars
- Publish corporate, fleet, RWA and workplace pages
- Repair blog archive and internal links
- Optimize verified Kanpur/Lucknow pages
- Begin first data-led PR asset
Proof + conversion
- Publish case studies and pricing factors
- Launch university/delivery pages where real
- Run CTA/form/WhatsApp tests
- Expand contextual internal links
- Measure indexation and qualified leads
- Reforecast from real performance
Weekly team operating model
Query/page mapping, briefs, technical QA, internal links, GSC analysis and revenue dashboard.
1 commercial page + 1 BOFU/MOFU article or case study weekly, both evidence-bound.
SSR/templates, redirects, analytics, schema, speed, form attribution and release QA.
10–15 researched pitches weekly, relationship follow-up, mention reclamation and PR distribution.
12-month forecast and KPI system
Scenarios, not promises
700 keywords, 1,500 traffic, 1% relevant-page conversion.
1,500 keywords, 5,000 traffic, 2% relevant-page conversion.
3,000 keywords, 12,000 traffic, 3% relevant-page conversion.
Models start from the 123 screenshot baseline. Outcomes depend on service-market fit, indexing, content quality, authority acquisition, conversion UX and sales execution. Reforecast monthly from actuals.
Final strategy
If Zeway can only do 10 things
- 01Validate the commercial truth.
Products, live cities, plans, pricing factors, sales ownership, lead values and delivery capacity.
- 02Export the missing data.
GSC, GA4, CRM, GBP and current Semrush/Ahrefs so priorities graduate from proxies to measured economics.
- 03Server-render priority routes.
Return the same main content, H1 and links in initial HTML, then hydrate the application.
- 04Rebuild the rental pillar.
Availability, plans, price factors, documents, use cases, proof and booking.
- 05Rebuild the charging pillar.
Site assessment, hardware/service choices, installation, maintenance, proof and lead qualification.
- 06Ship four B2B money pages.
Corporate/fleet, delivery, workplace and housing-society solutions.
- 07Own verified local demand.
Make Kanpur and Lucknow genuinely useful before adding any new city.
- 08Publish proof.
Named case studies, service methodology, transparent pricing logic and operational limitations.
- 09Build authority with data.
One original EV mobility dataset per quarter, distributed to the 140-prospect list.
- 10Measure qualified revenue.
Attribute every call, form, WhatsApp and app action to landing page, query theme, lead quality and closed revenue.
2 pillars, 6 B2B/service pages, 4 verified city/service pages, 4 pricing/comparison pages, 2 case studies and 2 data/FAQ assets.
Prioritize verified competitor-mention outlets, EV/auto editors, relevant business media, government/research citations, partners and real customer ecosystems.
10 BOFU buyer guides, 8 comparisons/pricing pieces, 6 fleet/charging implementation guides, 4 original-data stories and 2 policy explainers.
Spend 40% on money-page briefs/optimization, 25% technical/internal links, 15% measurement, 10% local/GEO and 10% outreach coordination.
Implementation library