Also Good
saascubes.com
Curated SaaS directory offering permanent do-follow backlinks for modern software products

AI home design tool using room photos and real furniture or plant references
Spaceora is an AI-powered home and garden design platform built for homeowners, real estate professionals, interior designers, and stylists. The application allows users to upload a photograph of a room, empty property listing, or garden to explore redesigns, virtual staging, and planting concepts. It offers specific tools for interior room layout changes, furniture replacement, exterior renovations, and landscape planning. For interior design, Spaceora integrates real furniture references from IKEA and Amazon, providing product specifications, dimensions, and purchasing links. For outdoor spaces, it filters plant species based on local US ZIP codes and USDA hardiness zones, taking sunlight and mature plant sizes into consideration. The platform provides starter credits with one free generation on sign-up, alongside paid subscription tiers.
“Spaceora is an AI-powered home and garden design platform that lets users redesign rooms, stage empty properties, replace furniture, and plan landscaping using photos combined with real IKEA and Amazon furniture references or climate-specific plant data.”
Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.
A language model processing this input learns that Spaceora provides a comprehensive suite of AI visual design tools for indoor and outdoor spaces. The provided homepage markdown covers the core features, targeted user groups, step-by-step user workflows, a frequently asked questions section, and specific blog guides. The llms.txt file adds a structured list of available tools, such as the rug size calculator and hardiness zone finder, as well as exact subscription tier names and monthly pricing details including starter credits, Lite, Pro, and Max plans. The JSON-LD blocks supply structured FAQ data and application metadata. Pricing details, subscription tiers, and tool breakdowns are present in the supplementary files rather than the main homepage text, while contact details and specific geographical availability outside supported regions are absent from the text entirely.
Good for Bots report
robots.txt is present and valid. robots.txt is valid, with 1 user-agent group.
Sitemap is present and parses. Sitemap declared in robots.txt, listing 74 URLs.
Describes itself to machines with schema.org JSON-LD. All 4 pages read pass. The homepage describes itself to machines as FAQPage, Question, Answer in valid schema.org JSON-LD.
Content is marked up so a reader can find it. All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
Navigation links expose usable destinations. 2 of 2 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 117 of 117 assessed homepage links and buttons have a nonempty accessible name.
Form fields have names and recognizable semantics. 10 of 10 assessed homepage form fields meet the static naming and field-semantics checks.
Controls expose roles, states and relationships. 136 of 136 assessed homepage controls and role declarations meet the static role, state and relationship checks.
Each page declares one usable canonical URL. All 4 pages read pass. The homepage declares itself as its canonical URL.
Section links reach an element on the page. The homepage has 2 section links, and every one reaches an element on the page.
llms.txt is present and well formed. /llms.txt is well formed: 45 links across 4 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is descriptive: a summary plus descriptions on 98% of links.
Serves markdown at its own URL. /llms-full.txt serves the site's content as markdown (11 KB).
States a position on AI crawlers. States a position on 6 AI crawlers, across 3 purposes (training, search, user-fetch).
Serves markdown when asked for it. None of the 4 pages read pass. Asking the homepage for markdown still returns text/html. +10 with its prompt.
Declares AI usage preferences. No usage declaration found in robots.txt or the final successful homepage response header. +2.5 with its prompt.
Advertises machine-readable resources with typed links. None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere. +1.3 with its prompt.
Earned
The whole readable base above the line, 36 of the 50 agent-layer points below it.
3 prompts away
For the owner of spaceora.app
They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.
Select a check to see what we found and how it is graded.
Readable base
50 / 50
3.3 of 3.3 points.
robots.txt is valid, with 1 user-agent group.
8.3 of 8.3 points.
Sitemap declared in robots.txt, listing 74 URLs.
8.3 of 8.3 points.
All 4 pages read pass. The homepage describes itself to machines as FAQPage, Question, Answer in valid schema.org JSON-LD.
10 of 10 points.
All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
4.2 of 4.2 points.
117 of 117 assessed homepage links and buttons have a nonempty accessible name.
2.5 of 2.5 points.
10 of 10 assessed homepage form fields meet the static naming and field-semantics checks.
2.5 of 2.5 points.
136 of 136 assessed homepage controls and role declarations meet the static role, state and relationship checks.
1.7 of 1.7 points.
All 4 pages read pass. The homepage declares itself as its canonical URL.
0.8 of 0.8 points.
The homepage has 2 section links, and every one reaches an element on the page.
Agent layer
36.3 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 45 links across 4 sections.
7.5 of 7.5 points.
/llms.txt is descriptive: a summary plus descriptions on 98% of links.
12.5 of 12.5 points.
/llms-full.txt serves the site's content as markdown (11 KB).
0 of 10 points.
None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.
5 of 5 points.
States a position on 6 AI crawlers, across 3 purposes (training, search, user-fetch).
0 of 2.5 points.
No usage declaration found in robots.txt or the final successful homepage response header.
0 of 1.3 points.
None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere.
Penalties
− 0
Penalty: 0 of 15 points.
Our crawler reaches the page without being challenged.
Penalty: 0 of 20 points.
Nothing on the homepage tells a crawler to skip it or to withhold its snippet.
Penalty: 0 of 25 points.
The captured homepage HTML contains 1420 content words; completeness is not assessed.
Penalty: 0 of 25 points.
robots.txt allows every known search and user-fetch crawler to reach the homepage.
Penalty: 0 of 10 points.
The homepage is served over HTTPS and returns HTTP 200.
Penalty: 0 of 3 points.
The homepage provides both a non-empty title and meta description.
Penalty: 0 of 3 points.
The homepage is reached in 0 redirects.
Penalty: 0 of 3 points.
The homepage reached a plain crawler in 81 ms.
Agent capabilities
0 of 11 · no points
Each one found adds +1 to the badge.
Adds +1 to the badge when found.
No API catalog published.
Adds +1 to the badge when found.
No /auth.md published.
Adds +1 to the badge when found.
No AI Catalog published, so no MCP server card can be discovered.
Adds +1 to the badge when found.
No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.
Adds +1 to the badge when found.
No usable Agent Skills index was found at either well-known path or in the AI Catalog.
Adds +1 to the badge when found.
No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.
Adds +1 to the badge when found.
No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.
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.
Adds +1 to the badge when found.
No ACP discovery declaration established at /.well-known/acp.json.
Adds +1 to the badge when found.
No UCP discovery declaration established at /.well-known/ucp.
Adds +1 to the badge when found.
No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.
It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.
Access & usage policy
GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.
Sampled URL: https://spaceora.app/
No matching refusal for this URL was found for the listed identities.
Declared allow · Scan admission
The recorded robots admission decision allowed our crawler to proceed.
GoodForBotsBot admission along the homepage request chain
https://spaceora.app/
Declared allow · robots.txt
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://spaceora.app/
https://spaceora.app/robots.txt
User-agent: * User-agent: gptbot User-agent: oai-searchbot User-agent: chatgpt-user User-agent: perplexitybot User-agent: claudebot User-agent: google-extended allow: /
robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers
GoodForBotsBot received HTTP 200 via a direct request.
Observed · Direct request
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://spaceora.app
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://spaceora.app/
HTTP 200 Transport: direct
Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge
No indexing restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No indexing restriction was observed in the supported homepage directives.
homepage response
https://spaceora.app/
No snippet restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No snippet restriction was observed in the supported homepage directives.
homepage response
https://spaceora.app/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://spaceora.app/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: ai-use; applicable robots group/path and this response's header
https://spaceora.app/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: train-ai; applicable robots group/path and this response's header
https://spaceora.app/
In its category
The prompts in the owner view would take Spaceora to 100, 2nd in its category.
To the prompts →Category average 61. The percentile appears once the catalogue holds a few hundred sites.
Every scan is kept. Pro draws the history as a chart →
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.
More like Spaceora:AI Products & AgentsDesignReal EstateAI & Machine Learning
Also Good
saascubes.com
Curated SaaS directory offering permanent do-follow backlinks for modern software products
Also AI & Machine Learning
goodforbots.com
Evaluates website readability for AI crawlers and language models with a scoring rubric
submitrocket.com
Same category
pathnovo.com
AI agents that parse engineering documents into structured data for enterprise systems
Do you run spaceora.app? Open the owner view → Removing the listing is free. Remove →