Spala
Visibility report

Spala Visibility Foundation Report

Current public status for the Spala visibility foundation: deployed pages, validation proof, indexability status, external directory status, and owner actions still needed.

Status

Foundation deployed and verified. Owner actions remain for Google/Bing indexing requests, Search Console refetch of the clean docs robots file, and third-party directory submissions that require account control.

What Was Deployed

Validation Evidence

EvidenceStatusURL
Visibility validation ledger25 pages checked, 50 captures, 0 needing reviewJSON / Markdown
Public indexability check25 pages checked, 25 technical passes, public indexing for new pages pendingJSON / Markdown
On-page SEO and internal-link check26 pages checked, 26 passing; 114 same-origin internal links checked, 0 brokenHTML / JSON / Markdown
Search indexing owner runbookExact Cloudflare, Google Search Console, Bing Webmaster, Rich Results, and priority URL submission actions preparedHTML / JSON / Markdown
Structured-data visibility check25 priority pages passing rendered JSON-LD checks; 5 standalone schema files parseable; Rich Results eligibility not claimedJSON / Markdown
Agent discovery link check410 Spala-owned discovery URLs checked, 410 passing, 0 brokenJSON / Markdown
Public web-search baseline12 queries checked; branded/MCP/pricing results visible; exact new pages and broad category visibility still not provenHTML / JSON
Goal completion auditRequirement-level status: foundation deployed, full goal not complete while owner actions and external proof remain pendingHTML / JSON
Visibility owner action boardCompact current queue for Search Console, Bing, Rich Results, Smithery, MCP.so, directories, Product Hunt, review proof, and OAuth-complete MCP handoff actionsHTML / JSON
Lighthouse visibility audit5 representative pages checked; SEO 100 on all checked pagesJSON / Markdown
Fresh-agent visibility audit3 scopes completed; MCP 8/10, start/pricing 6/10, trust/pricing 6/10; follow-up hardening deployedJSON / Markdown
Post-hardening fresh-agent retest2 scopes completed; start/pricing improved from 6/10 to 8/10; MCP stayed 8/10; project-auth proof still pendingJSON / Markdown
Public MCP auth proofOAuth metadata, 401 auth challenge, invalid-JSON error format, docs search, and CORS preflight verified; authenticated project transcript still pendingJSON / Markdown
External directory live checkOfficial MCP Registry and Glama live; Glama healthy and ownership verified; MCP.so and Smithery not live at checked URLsHTML / JSON / Markdown
Review proof capture runbookOwner runbook published; live reviews, customer quotes, case studies, Product Hunt proof, and community proof still not provenHTML / JSON
Directory visibility batchLive, with claim boundariesHTML
Directory submission field pack12 target-specific field-ready variants prepared; owner submission still requiredHTML / JSON / CSV
Public MCP server cardLiveserver-card.json
Homepage guardVerified clean13 bundle restored after deployHomepage

Lighthouse Snapshot

PagePerformanceAccessibilityBest practicesSEO
Home379477100
Backend for AI-built apps8610096100
Spala vs Xano589377100
MCP profile96100100100
Visibility foundation report98100100100

Follow-up: homepage blocking time and the Xano comparison page LCP should be reviewed without replacing the current homepage design or visual system.

Structured Data

Rendered structured-data verification now covers the 25 priority visibility pages. All 25 pages have parseable JSON-LD with expected schema types, and all 5 standalone schema JSON-LD files are reachable and parseable. This is structured-data hygiene evidence, not Google Rich Results approval or indexing proof.

Fresh-Agent Audit

ScopeScoreFinding
Onboarding/start/pay/create6/10Product and user fit were clear; start/pay/create path needed hardening.
MCP handoff8/10Public MCP versus project MCP boundary was mostly clear.
Competitor/trust/pricing6/10Comparisons were conservative; procurement-grade trust details remain incomplete.

Follow-up deployed: the pricing page now includes a starting checklist and service-led pricing clarification; the MCP profile now includes canonical agent bootstrap and project-tool response examples.

Post-hardening retest: start/pricing improved to 8/10 and MCP handoff stayed 8/10. Remaining gaps are account-specific checkout details, project-specific API proof, and a redacted OAuth-complete project MCP transcript.

Public MCP Auth Proof

Public MCP verification now confirms OAuth metadata discovery, HTTP 401 + WWW-Authenticate for unauthenticated project tools, relevant auth/project-handoff docs search, JSON-RPC parse errors for invalid JSON, and browser CORS preflight headers. The remaining proof gap is a redacted authenticated test account transcript showing project listing, project selection, returned project mcpUrl, and project MCP initialization.

Review Proof Capture Status

A public-safe owner runbook is now published for future G2, Capterra, TrustRadius, customer quote, case-study, Product Hunt, and community proof capture. This is a capture process, not live proof: current public evidence still does not prove reviews, customer logos, ratings, case studies, Product Hunt traction, compliance, SLA, or production trust parity.

Evidence: review proof capture runbook, JSON, and Markdown.

External Directory Status

TargetStatusProof or next action
Official MCP RegistryLiveLive listing
Glama MCPLive, healthy, ownership verifiedLive listing
MCP.soSubmitted, pending live listingSubmission evidence
SmitheryNot live at checked URL; ready for owner URL publishingUse MCP URL and server card.
Other directoriesPrepared, owner submission neededBetaList, AlternativeTo, SaaSHub, Futurepedia, TAAFT, Toolify, NoCodeFinder, DevHunt.
Directory field packPrepared, owner submission needed12 target-specific field variants.

Owner Actions Still Needed

Use the compact current owner-action queue at visibility owner action board or JSON.

  1. Follow the search indexing owner runbook.
  2. Confirm Google Search Console refetches the clean exact https://docs.spala.ai/robots.txt.
  3. Request indexing for priority URLs in Google Search Console.
  4. Submit sitemap or priority URLs in Bing Webmaster Tools.
  5. Submit Smithery with the hosted MCP URL and server card.
  6. Claim/verify Glama if owner analytics and listing control are needed.
  7. Submit prepared directory copy to the owner-action directories.
  8. Use the prepared Product Hunt packet, then add owner-approved media/account details before launch.
  9. Use the review proof capture runbook before publishing customer quotes, reviews, logos, case studies, Product Hunt proof, or community proof.

Claim Boundary

This report proves deployed public assets, technical renderability, screenshot evidence, conservative page metadata, and current public directory status. It does not prove Google/Bing indexing, rankings, AI answer citations, traffic, conversions, third-party reviews, compliance certification, SLA, or production suitability.

Last updated: July 10, 2026.