Spala Search Indexing Owner Runbook
Exact owner-side actions for Google Search Console, Bing Webmaster Tools, docs robots refetching, sitemap submission, priority URL inspection, and Rich Results checks.
Status Boundary
This runbook is an action checklist. It does not prove Google indexing, Bing indexing, rankings, impressions, clicks, AI answer citations, conversions, or Rich Results eligibility.
Current Evidence
- Public indexability check: public-indexability-check-2026-07-10.json
- Structured-data visibility check: structured-data-visibility-check-2026-07-10.json
- Visibility foundation report: visibility-foundation-report-2026-07-10
- Current public technical state: 25 priority pages checked, 25 technical passes, 0 needing review.
- Current rendered schema state: 25 priority pages checked, 25 schema passes, 5 standalone schema files parseable.
Docs Robots Status
The exact public robots URL is clean:
https://docs.spala.ai/robots.txt
The valid expected body is:
User-agent: * Allow: / Sitemap: https://docs.spala.ai/sitemap.xml
The deployed origin may also include LLM links as comments. That is valid robots syntax:
# LLM context: https://docs.spala.ai/llms.txt # Full LLM context: https://docs.spala.ai/llms-full.txt
No Cloudflare purge is currently needed. If a stale file with bare LLMs: directives appears again, purge exactly https://docs.spala.ai/robots.txt.
Grant Access Safely
Google Search Console
- Open Google Search Console and choose the verified
spala.aiproperty. - Go to Settings -> Users and permissions -> Add user.
- Add the collaborator's Google Account email.
- Use Restricted for view-only review, Full for sitemap submission and URL Inspection work, and Owner only for someone who should manage users and verification.
- Avoid service-account emails for normal UI access. Search Console UI users need valid Google Accounts; service accounts are for API workflows and often cannot be added as UI users.
- Remove or downgrade temporary access after the checks are complete.
Official reference: Manage users, owners, and permissions.
Bing Webmaster Tools
- Open Bing Webmaster Tools and choose the verified
spala.aisite. - Open User Management / Users.
- Add the collaborator email and choose the minimum access needed for sitemap and URL submission checks.
- If access does not work, confirm the email is tied to an account Bing accepts, then retry or use owner-operated screen sharing.
- Remove temporary access after the checks are complete.
Official reference: How to add users to your site account.
Google Search Console Actions
- Open the
spala.aiproperty in Google Search Console. - Go to Settings -> robots.txt and confirm
https://docs.spala.ai/robots.txtno longer reports syntax errors after Google refetches the clean exact URL. - Submit or resubmit
https://spala.ai/sitemap.xml. - Use URL Inspection for each priority URL below. If the live test passes, request indexing.
- Record inspection status, crawl state, indexing state, selected canonical, and any errors in an owner-only tracker.
Bing Webmaster Actions
- Open the
spala.aisite in Bing Webmaster Tools. - Submit or resubmit
https://spala.ai/sitemap.xml. - Use URL Submission for the same priority URL list below, respecting account quota.
- Record submitted, indexed, discovered, crawl error, and canonical statuses in the owner tracker.
Rich Results Follow-Up
Run Google Rich Results Test for pages with FAQPage, Product, ItemList, BreadcrumbList, or SoftwareApplication schema. Record eligible result types and warnings. Local JSON-LD parseability is useful hygiene evidence, but it is not Rich Results approval.
Priority URLs
| URL | Target query | Status | Rich Results priority |
|---|---|---|---|
| https://spala.ai/ | Spala AI backend builder | technical pass | yes |
| https://spala.ai/backend-for-ai-built-apps/ | backend for AI-built apps | technical pass | yes |
| https://spala.ai/backend-for-mvps/ | backend for MVPs | technical pass | yes |
| https://spala.ai/backend-for-lovable-bolt-cursor-apps/ | backend for Lovable Bolt Cursor apps | technical pass | yes |
| https://spala.ai/compare/xano/ | Spala vs Xano | technical pass | yes |
| https://spala.ai/compare/supabase/ | Spala vs Supabase | technical pass | yes |
| https://spala.ai/compare/convex/ | Spala vs Convex | technical pass | yes |
| https://spala.ai/compare/firebase/ | Spala vs Firebase | technical pass | yes |
| https://spala.ai/compare/bubble/ | Spala vs Bubble | technical pass | yes |
| https://spala.ai/alternatives/xano/ | Xano alternatives | technical pass | yes |
| https://spala.ai/mcp-profile/ | Spala MCP | technical pass | no |
| https://spala.ai/directory-visibility-batch-2026-07-10/ | Spala directory listings | technical pass | yes |
| https://spala.ai/external-submission-tracker/ | Spala external submission tracker | technical pass | no |
| https://spala.ai/search-indexing-owner-runbook-2026-07-10/ | Spala search indexing owner runbook | technical pass | no |
| https://spala.ai/visibility-owner-action-board/ | Spala visibility owner action board | technical pass | no |
| https://spala.ai/review-proof-capture-runbook/ | Spala review proof capture runbook | technical pass | no |
| https://spala.ai/visibility-foundation-report-2026-07-10/ | Spala visibility foundation report | technical pass | no |
| https://spala.ai/visibility-goal-completion-audit-2026-07-10/ | Spala visibility goal completion audit | technical pass | no |
| https://spala.ai/pricing/ | Spala pricing | technical pass | yes |
| https://spala.ai/security/ | Spala security | technical pass | no |
| https://spala.ai/limits/ | Spala limits | technical pass | no |
| https://spala.ai/export-deletion/ | Spala export deletion | technical pass | yes |
| https://spala.ai/trust/ | Spala trust | technical pass | no |
| https://spala.ai/privacy/ | Spala privacy | technical pass | no |
| https://spala.ai/terms/ | Spala terms | technical pass | no |