Your robots.txt invites GPTBot, ClaudeBot and PerplexityBot in because "Any&All wants to be cited in AI answers". But the pages that answer the questions buyers and sellers actually ask (what it costs, how it works, who runs it, help) come back as one empty 4 KB shell with the homepage title and no canonical; the words only appear after JavaScript runs. Most AI crawlers and every WhatsApp or Instagram link preview do not run JavaScript, so to them /pricing is the homepage with nothing in it. The blog is already served as full HTML with FAQ data, which shows the fix works on this site.
First action
Fetch /pricing with curl and confirm the fee table is in the HTML.
How to measure it
Static pages indexed correctly
- Now
- –
- Target
- 10 of 10
- By
- 30 days
Steps
List the pages
The ten static URLs plus help-center categories and articles.
Growth Lead 1 hour
Prerender them
Reuse the blog's build step for /pricing, /how-it-works, /about, /help-center, /contact and the legal pages.
Frontend Engineer 3 days
Write the head tags
Own title, description, canonical and Open Graph image per page.
Growth Lead 1 day
Add structured data
FAQPage on pricing and help, Organization on about.
Frontend Engineer 1 day
Extend the sitemap
Help-center articles into sitemap-pages.xml.
Frontend Engineer 2 hours
Verify
curl each page; URL inspection in Search Console; a WhatsApp preview test.
Growth Lead 1 day
Track
Impressions and AI-referral visits to the static pages.
Growth Lead weekly
Why it works
Prerender the ten static pages at build time the same way the blog is built: each with its own title, description, canonical and Open Graph tags, the visible text in the HTML, FAQPage data on /pricing and /help-center, and Organization data on /about. Add the help center's category and article pages to the sitemap, then re-submit it and check the pages in Search Console's URL inspection.
A growth lead's first channel for a pre-launch marketplace is organic and AI-answer discovery, and those systems can only cite pages they can read. This is a build change, not new content.
Ready to use
ChecklistStatic page check
[ ] curl shows the page text [ ] Own <title> and description [ ] Self-canonical [ ] Open Graph title and image [ ] FAQPage or Organization data [ ] Listed in sitemap-pages.xml [ ] WhatsApp preview shows the right title
Risks and how to handle them
Prerendered text drifts from the app
Generate both from the same source files.
Evidence
- Your websiteThe raw HTML served for anynall.com/, /pricing, /about, /how-it-works and /help-center (checked November 4, 2026) is the same 4 KB file: the title "Any & All - Live Shopping & Auctions for India", the homepage description, no canonical tag and an empty <div id="root"></div>. The page text only appears after JavaScript runs. Blog posts, by contrast, are served as full HTML with their own title, canonical, BlogPosting and FAQPage data.Source
- Your websiterobots.txt lets GPTBot, ClaudeBot, PerplexityBot, Google-Extended and other AI crawlers in on purpose: "Any&All wants to be cited in AI answers, so these must be able to read the site." The sitemap lists 10 static pages and 57 blog posts; the category, seller, listing and stream-recap sitemaps are "Empty on purpose": "/sneakers, /category/sneakers and every other category path render the home page", public seller profiles at /@handle have not shipped, and "Finished streams have no recap page on the website yet".Source
- Your websiteThe blog has 58 posts, the latest dated October 31, 2026: buyer guides ("How to spot fake sneakers in India", "Legit Check Air Jordan 1", "Perfume Batch Codes", "pokemon-cards-india-buying-guide", "buy-pre-owned-luxury-watch-india", "card-breaks-explained"), trust guides ("upi-scams-collectors", "avoid-instagram-reseller-scams") and seller guides ("gst-for-online-resellers", "first-live-selling-show", "how-to-price-preowned", "instagram-vs-marketplace-selling"). Every post is in English.Source