The site targets a small set of distinct English search intents rather than producing many thin variations:
| Query / intent | Primary page |
|---|---|
| road trip bingo online / free road trip bingo online | / and /road-trip-bingo-online |
| road trip bingo for kids | /road-trip-bingo-for-kids |
| multiplayer road trip bingo | /multiplayer-road-trip-bingo |
| car bingo | /car-bingo |
| how to play road trip bingo | /how-to-play-road-trip-bingo |
The playable homepage remains the primary experience. Crawlable explanatory content, visible frequently asked questions, real board examples, safety guidance, and links to the focused guides follow the game launcher. Every guide answers a different user need and links back to the playable game.
Seed-based /bingo URLs are shareable product state, not search landing pages. They intentionally use noindex,follow and canonicalize to /bingo so arbitrary seeds do not create an unlimited set of low-value indexed pages.
Remix server-renders the homepage, search guides, metadata, canonical links, internal links, and structured data. Important SEO content does not depend on client interaction.
Metadata is built by @/lib/seo.ts and includes:
- A unique title and description for every indexable page
- Self-referencing canonical URLs on
https://roadtripbingo.app - Open Graph title, description, URL, locale, image dimensions, and image alt text
- Twitter large-image metadata
- An explicit indexing directive for public content
The old roadtrip-bingo.netlify.app hostname redirects to the canonical custom domain through netlify.toml. The social image also uses the current domain and verified product claims.
public/sitemap.xml contains the homepage and the five indexable search guides. It excludes parameterized game boards and 404 pages.
public/robots.txt:
- Allows normal search crawling
- Explicitly allows
OAI-SearchBotfor ChatGPT search discovery - Disallows
GPTBot, which is the separate OpenAI training crawler - Advertises the canonical sitemap URL
The homepage contains a Schema.org WebApplication object with only verifiable product attributes. Each search guide contains a WebPage object connected to the application and site.
The visible FAQ is intentionally not marked up as FAQPage. Google removed FAQ rich results in May 2026, so that markup would add maintenance without a Google search feature benefit. No ratings, reviews, usage totals, or fabricated offers are included.
The game supports nine board languages selected through the language query parameter. These parameters represent game state; they are not separate translated editorial pages and /bingo is not indexed. The document language follows a valid requested game language, including nb for the app's Norwegian option.
No hreflang links are emitted because there are currently no equivalent, separately indexable translated URLs. If full translated landing pages are added later, give each translation a stable path, translated metadata and content, a self-canonical, and reciprocal hreflang links including x-default.
The added copy is server-rendered semantic HTML and uses the existing CSS and local fonts. It adds no SEO library, analytics dependency, remote font, large image, or new client-side interaction. Production builds should be monitored for Core Web Vitals: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS).
The current production build reports approximately:
- Shared SEO content: 5.75 kB gzip
- Homepage route: 26.58 kB gzip
- Existing bingo route: 225.08 kB gzip
- Main Tailwind stylesheet: 17.21 kB gzip
These are build artifacts, not field performance measurements. Use Search Console Core Web Vitals and a Chrome/Lighthouse trace after deployment to confirm real-device performance.
- Verify the apex and
wwwdomain properties in Google Search Console. - Submit
https://roadtripbingo.app/sitemap.xmlin Google Search Console. - Inspect the homepage and each guide with Search Console's URL Inspection tool after deployment.
- Add and verify the site in Bing Webmaster Tools, then submit the sitemap there.
- Monitor impressions, clicks, click-through rate, indexed-page coverage, and query positions by landing page.
- Validate deployed JSON-LD with Schema.org Validator and inspect the rendered source with Google's URL Inspection tool.
- Confirm the Netlify subdomain returns a permanent redirect after deployment.
- Seek relevant links from family travel sites, road-trip guides, parenting resources, and travel-game roundups. Useful editorial mentions matter more than creating more near-duplicate landing pages.
- Consider IndexNow only if the site begins publishing or updating URLs frequently. Six mostly static pages do not currently justify an automated submission integration.
llms.txt is not implemented. Google states that it is not needed for Google Search, while discoverability for ChatGPT search is controlled through OAI-SearchBot and normal crawlable pages.