schedulala.comscanned Aug 4, 2026 · 11:020.62s
Public AI visibility report

schedulala.comAI visibilityNeeds Work

This site has a useful foundation, but important gaps still limit AI readability.

Key strengths include AI guidance file and sitemap, while plain-text page access and content signals need attention.

Recommended next step

add content negotiation for Accept: text/markdown on the homepage and return a markdown representation with Content-Type: text/markdown.

Keep the HTML response for regular browser requests.

Overall score

61/100
Needs Work

What happens next

Monitor this score as your site changes

Weekly checks catch robots, sitemap, schema, and content regressions before AI systems stop reusing your pages.

Monitor changes
Download PDF
Go to fixesOverall position358 out of 1,488Leaderboard

// score breakdown

Points by check

8 checks

Crawlability10/20
Robots.txt7.5/15
llms.txt15/15
Sitemap10/10
Markdown support0/15
Semantic HTML8.6/10
Structured data10/10
Content signals0/5
3pass3warn2fail

Public link

llmscan.dev/scan/bbS4fyS2sHcjCvyexvJpK

Signals checked

8 AI visibility signals

Fix bundle

4 copy-ready files

Share badge

Needs Work · 61/100

Add a polished proof badge

A compact badge for footer, press, or trust sections that links visitors to this public report.

Embed codellmscan.dev/scan/bbS4fyS2sHcjCvyexvJpK
<a href="https://www.llmscan.dev/scan/bbS4fyS2sHcjCvyexvJpK"
  target="_blank"
  rel="noopener"
>
  <img
    src="https://www.llmscan.dev/scan/bbS4fyS2sHcjCvyexvJpK/badge.png"
    alt="LLM Scan AI visibility score badge"
    width="460"
    height="120"
    style="width: 260px; max-width: 100%; height: auto;"
  />
</a>
Open badge
L
LLM Scan
Needs Work
Score
61/100

Share your score

Post the public report with: “We scored 61/100 for AI-readability.”

Download fixes

Grab generated files and implementation notes for the highest-impact gaps.

Rescan weekly

Save this domain to catch regressions after content, sitemap, or robots changes.

Monitor weekly

// signal breakdown

8 signals AI systems depend on

The homepage is reachable, but robots.txt contains AI crawler restrictions for GPTBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, and Google-Extended.

Signal weight

10/20
Warn

Evidence

url
https://schedulala.com/
finalUrl
https://schedulala.com/
status
200

Recommendation

Next step: Review AI crawler Disallow rules and keep only the paths that should be excluded from AI crawler access; serve a non-empty HTML homepage with a canonical link tag.

robots.txt contains AI-crawler path blocks for GPTBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, and Google-Extended.

Signal weight

8/15
Warn

Evidence

robotsTxtUrl
https://schedulala.com/robots.txt
exists
true
rawRobotsTxt
# Schedulala.com Robots.txt # Updated: July 30, 2026 # # IMPORTANT — why there are no per-bot groups below: # Per the robots.txt standard, a crawler obeys exactly ONE group: the most # specific matching User-agent. Named groups do NOT inherit rules from the # "*" group (https://developers.google.com/search/docs/crawling-indexing/robots/robots_txt). # This file previously listed ~32 AI crawlers each with a bare "Allow: /", # which silently exempted every one of them from all the Disallow rules — # bingbot, GPTBot, ClaudeBot and others could crawl /api/, /admin/, /auth/, # /dashboard and the test pages. # Since we want AI crawlers to have the SAME access as everyone else (all # public content, none of the private paths), the "*" group below already # does that. Do not re-add per-bot "Allow: /" groups. Only name a crawler # here if it genuinely needs DIFFERENT rules, and if you do, repeat the full # Disallow list inside that group. User-agent: * # Allow important pages Allow: / Allow: /pricing Allow: /threads Allow: /instagram Allow: /twitter Allow: /tiktok Allow: /facebook Allow: /linkedin Allow: /bluesky Allow: /youtube Allow: /pinterest Allow: /telegram # Allow blog and tools content Allow: /blog/ Allow: /tools/ # Allow developer platform and AI integration pages Allow: /developers Allow: /developers/docs Allow: /integrations/ Allow: /agents/ # Allow localized blog content Allow: /es/blog/ Allow: /de/blog/ Allow: /ja/blog/ Allow: /fr/blog/ Allow: /pt/blog/ Allow: /ko/blog/ Allow: /it/blog/ Allow: /nl/blog/ Allow: /zh/blog/ Allow: /ar/blog/ # Allow comparison pages Allow: /compare/ # Disallow API endpoints Disallow: /api/ # Disallow authentication and private app pages Disallow: /auth/ Disallow: /admin/ Disallow: /api/auth/ Disallow: /dashboard # Disallow private/deprecated pages Disallow: /connect Disallow: /platform-disclosure # Block oauth callback (not a real page) Disallow: /oauth/callback # Block data deletion page (privacy policy, not searchable content) Disallow: /data-deletion # Note: /blog/category/ pages use page-level noindex for empty categories, # so they don't need a robots.txt Disallow. Categories with articles should be indexable. # Disallow test pages Disallow: /test-* Disallow: /welcome Disallow: /oauth Disallow: /debug-* Disallow: /bluesky-fix Disallow: /bluesky-test Disallow: /twitter-test # NOTE on /_next/ — deliberately NOT blocked. # Blocking /_next/static/ blocks the CSS and JS bundles Google needs to render # pages. Every tool widget under /tools/ is a client component, so with those # chunks blocked Googlebot renders 130+ "free tool" pages as an unstyled page # with a dead input. Google: "Google Search won't render JavaScript from # blocked files" and "if the absence of these resources make the page harder # for Google's crawler to understand the page, don't block them." # The old justification comment here claimed the broader "Allow: /" would still # let Google fetch them — that is false; the more specific Disallow wins. # Static assets are not indexed as pages, so there is nothing to suppress. # NOTE on /platforms/ — deliberately NOT blocked. # Those URLs 301 to the canonical /{platform} pages. Blocking a redirect stops # Google from following it, so the link signals never consolidate. The old # comment claimed blocking "saves crawl budget"; crawl budget applies to sites # with 1M+ pages (or 10k+ changing daily). This site has ~740 URLs. # Sitemap Sitemap: https://schedulala.com/sitemap.xml # LLM-specific content files for AI crawlers # See https://llmstxt.org for specification # Concise overview: https://schedulala.com/llms.txt # Full documentation: https://schedulala.com/llms-full.txt

Recommendation

Next step: Review AI crawler Disallow rules and keep only the paths that should be excluded from AI crawler access.

The llms.txt file was found and includes the expected text, length, heading, and URL signals.

Signal weight

15/15
Pass

Evidence

llmsTxtUrl
https://schedulala.com/llms.txt
present
true
accessible
true

The sitemap index is valid and the checked child sitemap contains URL entries.

Signal weight

10/10
Pass

Evidence

sitemapUrl
https://schedulala.com/sitemap.xml
sitemapUrls
[https://schedulala.com/sitemap.xml]
robotsSitemapUrls
[]

The homepage returned HTML when requested with Accept: text/markdown, so the server appears to ignore markdown content negotiation.

Signal weight

0/15
Fail

Evidence

url
https://schedulala.com/
acceptHeader
text/markdown
status
200

Recommendation

Next step: Add content negotiation for Accept: text/markdown on the homepage and return a markdown representation with Content-Type: text/markdown. Keep the HTML response for regular browser requests.

The homepage has some semantic HTML signals, but one or more title, metadata, heading, landmark, content, or link text checks need improvement.

Signal weight

9/10
Warn

Evidence

url
https://schedulala.com/
quality
partial
score
86

Recommendation

Next step: Add missing semantic elements: article.

Valid JSON-LD structured data was found with core Organization or WebSite schema.org types.

Signal weight

10/10
Pass

Evidence

url
https://schedulala.com/
quality
good
hasStructuredData
true

Content-Signal directive not detected in headers, HTML metadata, or robots.txt.

Signal weight

0/5
Fail

Evidence

url
https://schedulala.com/
hasContentSignals
false
hasContentSignalHeader
false

Recommendation

Next step: Add the standard directive 'Content-Signal: ai-train=no, search=yes, ai-input=yes' to robots.txt, HTML metadata, or HTTP headers so AI systems can discover content usage preferences.

What happens next

Keep watching this score

Scores move when sites and models change. This one was measured once, on Aug 4, 2026.

Watch weekly

// generated fixes

Downloadable fix files

Preview the generated files below. Enter your email to reveal the full fixes, download the bundle, or copy the agent-ready implementation prompt.

Done-for-you

Agency package

Not sure how to ship the technical fixes? Book a call and we can help turn this report into implemented updates.

Fix planning from your scan

Implementation guidance

AI visibility monitoring

llms.txtMarkdown
# Schedulala - Schedule Social Media Posts to 12+ Platforms | Schedulala > Schedule posts to Instagram, TikTok, Bluesky, Twitter, LinkedIn, YouTube, and more from one dashboard. Start your free trial today. This llms.txt file summarizes the public, canonical resources that AI assistants and crawlers should use to understand this site. ## Site Overview - Canonical URL: https://schedulala.com/- Site type: organization
robots.txtTXT
# robots.txt additions# Copy these blocks into the existing robots.txt file. Keep current rules unless a note calls out a conflicting Disallow. # AI crawler access# Add explicit Allow rules for blocked AI crawlers; remove or narrow conflicting Disallow rules if your crawler target requires precedence.User-agent: GPTBotAllow: / User-agent: ChatGPT-UserAllow: /
schema.jsonJSON
{  "@context": "https://schema.org",  "@graph": [    {      "@type": "Organization",      "@id": "https://schedulala.com/#organization",      "name": "Schedulala - Schedule Social Media Posts to 12+ Platforms | Schedulala",      "description": "Schedule posts to Instagram, TikTok, Bluesky, Twitter, LinkedIn, YouTube, and more from one dashboard. Start your free trial today.",      "url": "https://schedulala.com/",      "logo": "https://schedulala.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Ficon.4ef400ea.png&w=48&q=75&dpl=dpl_HD9QFzFZUznjE2SUX1pKNU2BHSFU",
head metaHTML
# Content-Signal recommendations Use these directives to make AI-use preferences explicit for compliant crawlers and AI systems. They are advisory signals, so keep them aligned with robots.txt, terms, and access controls. ## Recommended values - ai-train=no: AI model training, fine-tuning, and dataset creation.- search=yes: AI search indexing, snippets, and discovery.- ai-input=yes: AI answer grounding, retrieval, and generated-response context.

What happens next

Monitor this score as your site changes

Weekly checks catch robots, sitemap, schema, and content regressions before AI systems stop reusing your pages.

Watch weekly

Related scans

Similar AI visibility reports

Browse leaderboard