Skip to content
Good for Bots

Travel Itinerary Template

travelitinerarytemplate.app

Online travel itinerary planner with day-by-day templates, exported to PDF, Google Docs or Excel

Good for Bots: Good, 75 of 100Get this badge →

On your homepage, it turns this report’s link to travelitinerarytemplate.app dofollow.

Scanned

What is Travel Itinerary Template?

Travel Itinerary Template is a free online travel itinerary planner, as the site's llms.txt and JSON-LD describe it. It offers 1,215 editable day-by-day itineraries in 100 countries plus a blank planner, and a visitor can pick a trip by country, trip length or style. An AI chat can change a plan on request, such as adding a day or slowing the pace. Plans can be printed in decorative designs or downloaded as PDF, Google Docs, Excel, Google Sheets, CSV or a calendar file, and downloads require a free account. The input lists Pro plans at $5.99 a month, $49.99 a year or $9.99 for a 30-day Trip Pass. It appears aimed at individual travelers planning trips, though the input does not say this directly.

Through a bot’s eyes

“Travel Itinerary Template is a free online travel itinerary planner with 1,215 day-by-day itineraries in 100 countries, which can be tailored with an AI chat and downloaded as PDF, Google Docs, Excel or Sheets.”

Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

A model reading this input learns that the homepage is about planning travel itineraries with AI and printing them in styled designs such as florals, bows and retro looks, and it names sample destinations including Venice, Bali, Lisbon, Paris and Kyoto. The visible homepage text gives the counts of 1,200+ itineraries and 100+ PDF designs, names the export formats PDF, Google Docs, Excel and Sheets, and offers a sign-up button. The homepage excerpt is truncated, so later content is missing. The llms.txt adds pricing tiers, AI chat message limits, the account requirement for downloads, a list of free tools and format pages, and a note that opening hours and prices in itineraries are not live data. The JSON-LD adds the publisher name Brandvio LLC, a support email, a Sacramento business address and WebApplication offers with the same prices. Contact details and pricing are therefore present as text, mostly through the supplementary files rather than the homepage body.

What stays hidden

The input does not show the content of any individual itinerary, so a model cannot tell what a day plan looks like or how detailed its sights and meals are. The homepage excerpt is truncated, and the design list gives names with only a few descriptive words. The input says little about how the AI tailors a plan beyond the chat summary, and the sources behind the routes are covered by a single short note.

Good for Bots report

Travel Itinerary Template scores 75 of 100: 45 of the 50 base points, 30 of the 50 agent-layer points, no penalties.

Earned

45 of the 50 base points above the line, 30 of the 50 agent-layer points below it.

75

Still open

Behind the checks below, with prompts in Pro.

2
Penalties0
How scoring works · current methodology →

For the owner of travelitinerarytemplate.app

3 prompts, 23 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

Select a check to see what we found and how it is graded.

Readable base

45 / 50

Passes.

3.3 of 3.3 points.

robots.txt is valid, with 2 user-agent groups.

Passes.

8.3 of 8.3 points.

Sitemap declared in robots.txt, listing at least 200 URLs.

Passes.

8.3 of 8.3 points.

All 4 pages read pass. The homepage describes itself to machines as Organization, Brand, PostalAddress in valid schema.org JSON-LD.

Half passes.

5 of 10 points.

2 of 4 pages read pass; 1 partly. The page at /pricing is barely structured: The content root holds only 33% of the page's words; most of the content sits outside it.

Passes.

8.3 of 8.3 points.

26 of 26 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

231 of 231 assessed homepage links and buttons have a nonempty accessible name.

Passes.

2.5 of 2.5 points.

7 of 7 assessed homepage form fields meet the static naming and field-semantics checks.

Passes.

2.5 of 2.5 points.

250 of 250 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Passes.

1.7 of 1.7 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

30 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 93 links across 6 sections.

Fails.

0 of 7.5 points.

/llms.txt is a bare link list: 18 of 93 links have a description.

Passes.

12.5 of 12.5 points.

llms.txt points at 92 markdown versions of pages.

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Passes.

5 of 5 points.

States a position on 11 AI crawlers, across 3 purposes (search, user-fetch, training).

Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Prompt in Pro →

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 2515 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 532 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Site profile

Login
Detected
A sign-in or sign-up link
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://travelitinerarytemplate.app/

Measured, our crawler
HTTP 200
GoodForBotsBot received HTTP 200 via a direct request.
Search and user-fetch crawlers refused
0 of 20
robots.txt refuses none of them.
Training crawlers refused
0
Refusing training would not change the score.

Crawlers and what robots.txt declares for them

Rules for the sampled URL, read the way RFC 9309 reads them. These are declarations, not access tests.

Crawlers and what robots.txt declares for them on the sampled URL
CrawlerPurposeDeclared accessScore effectRule that applies
Our crawler, measured
GoodForBotsBotGood for BotsSite diagnosticsFetchedHTTP 200, directNot scoredrobots.txt admitted our crawler
Search and AI answers
OAI-SearchBotOpenAIAI searchAllowedNoneUser-agent: oai-searchbot User-agent: chatgpt-user User-agent: gptbot User-agent: claude-searchbot User-agent: claude-user User-agent: claudebot User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: bingbot User-agent: duckassistbot Allow: /
Claude-SearchBotAnthropicAI searchAllowedNoneUser-agent: oai-searchbot User-agent: chatgpt-user User-agent: gptbot User-agent: claude-searchbot User-agent: claude-user User-agent: claudebot User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: bingbot User-agent: duckassistbot Allow: /
PerplexityBotPerplexityAI searchAllowedNoneUser-agent: oai-searchbot User-agent: chatgpt-user User-agent: gptbot User-agent: claude-searchbot User-agent: claude-user User-agent: claudebot User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: bingbot User-agent: duckassistbot Allow: /
DuckAssistBotDuckDuckGoAI searchAllowedNoneUser-agent: oai-searchbot User-agent: chatgpt-user User-agent: gptbot User-agent: claude-searchbot User-agent: claude-user User-agent: claudebot User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: bingbot User-agent: duckassistbot Allow: /
GooglebotGoogleSearchAllowedNot scoredNot named; User-agent: * applies
BingbotMicrosoftSearchAllowedNot scoredUser-agent: oai-searchbot User-agent: chatgpt-user User-agent: gptbot User-agent: claude-searchbot User-agent: claude-user User-agent: claudebot User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: bingbot User-agent: duckassistbot Allow: /
, all allowed
Fetches a person asked for
ChatGPT-UserOpenAIUser fetchAllowedNoneUser-agent: oai-searchbot User-agent: chatgpt-user User-agent: gptbot User-agent: claude-searchbot User-agent: claude-user User-agent: claudebot User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: bingbot User-agent: duckassistbot Allow: /
Claude-UserAnthropicUser fetchAllowedNoneUser-agent: oai-searchbot User-agent: chatgpt-user User-agent: gptbot User-agent: claude-searchbot User-agent: claude-user User-agent: claudebot User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: bingbot User-agent: duckassistbot Allow: /
Perplexity-UserPerplexityUser fetchAllowedNoneUser-agent: oai-searchbot User-agent: chatgpt-user User-agent: gptbot User-agent: claude-searchbot User-agent: claude-user User-agent: claudebot User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: bingbot User-agent: duckassistbot Allow: /
, all allowed
Model training, never scored
GPTBotOpenAIAI trainingAllowedNoneUser-agent: oai-searchbot User-agent: chatgpt-user User-agent: gptbot User-agent: claude-searchbot User-agent: claude-user User-agent: claudebot User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: bingbot User-agent: duckassistbot Allow: /
ClaudeBotAnthropicAI trainingAllowedNoneUser-agent: oai-searchbot User-agent: chatgpt-user User-agent: gptbot User-agent: claude-searchbot User-agent: claude-user User-agent: claudebot User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: bingbot User-agent: duckassistbot Allow: /
Applebot-ExtendedAppleAI trainingAllowedNoneUser-agent: oai-searchbot User-agent: chatgpt-user User-agent: gptbot User-agent: claude-searchbot User-agent: claude-user User-agent: claudebot User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: bingbot User-agent: duckassistbot Allow: /
Google-ExtendedGoogleAI training, GroundingAllowedNoneUser-agent: oai-searchbot User-agent: chatgpt-user User-agent: gptbot User-agent: claude-searchbot User-agent: claude-user User-agent: claudebot User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: bingbot User-agent: duckassistbot Allow: /
, all allowed
Agents, extraction and others
, all allowed

The robots.txt groups behind this table

User-agent: oai-searchbot
User-agent: chatgpt-user
User-agent: gptbot
User-agent: claude-searchbot
User-agent: claude-user
User-agent: claudebot
User-agent: perplexitybot
User-agent: perplexity-user
User-agent: google-extended
User-agent: applebot-extended
User-agent: bingbot
User-agent: duckassistbot
Allow: /

User-agent: *
Allow: /

https://travelitinerarytemplate.app/robots.txt

How to read this table

Each row says what robots.txt asks of that crawler. It does not show whether the crawler obeys, or how a firewall treats it. We measured only our own request.

Refusing search or user-fetch crawlers costs points under AI crawler access. Refusing training crawlers costs nothing.

Indexing directives, Content-Signal and AIPREF preferences are in the tabs below.

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://travelitinerarytemplate.app/

    robots.txt is present and valid

  • Observed · Direct request

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    Our request received HTTP 200. A status alone does not identify a WAF.

    Our recorded direct transport attempt; intermediate attempt URLs are not retained

    https://travelitinerarytemplate.app

    HTTP 200

    Serves the homepage over HTTPS with HTTP 200

  • Observed · Final homepage response

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    GoodForBotsBot received HTTP 200 via a direct request.

    homepage response

    https://travelitinerarytemplate.app/

    HTTP 200
    Transport: direct

    Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge

Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

In its category

19th of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 19Travel Itinerary Template · this reporttravelitinerarytemplate.app

The prompts in the owner view would take Travel Itinerary Template to 98, 2nd in its category.

To the prompts →

Category average 58. The percentile appears once the catalogue holds a few hundred sites.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
11 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
2.8 MB
Took
16.4 s
Homepage
532 ms · direct
Pages read
4
robots.txt
allowed
Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

  • Homepagealways read
  • /guides/what-is-a-travel-itineraryarticle · linked from the homepage · from the sitemap · read
  • /guidescollection · linked from the homepage · from the sitemap · read
  • /pricingpricing · linked from the homepage · from the sitemap · read

More like Travel Itinerary Template:SaaS & Web AppsProductivityTravel & HospitalityFreemium

Same category

vouchgeo.com

Tracks how AI assistants mention a brand across multi-question buying conversations

Same category

talhabashir.com

Free online calculators and tools for US taxes, mortgages, business and personal finance

Also Freemium

saascubes.com

Curated SaaS directory offering permanent do-follow backlinks for modern software products

Also Freemium

dolaai.pro

AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor

Also Freemium

brivoy.com

Community site where makers launch new products and early adopters discover them

volanea.com

Transactional email, campaigns, and automation API with AI agent support

Do you run travelitinerarytemplate.app? Open the owner view → Removing the listing is free. Remove →