AI PlazaAI Plaza
Start Free

Getting started · 12 min read

Get indexed on Google (Search Console)

Verify aiplaza.app in Google Search Console, submit sitemap.xml, and request indexing for AI Plaza homepage, docs, tools, and pricing pages.

· · AI Plaza

Quick steps

  1. Step 1. Open Search Console

    Go to https://search.google.com/search-console and sign in with the Google account that should own aiplaza.app.

  2. Step 2. Add the domain property

    Prefer a Domain property for aiplaza.app (covers www and apex). Use DNS TXT if you control DNS, or URL-prefix https://aiplaza.app with HTML meta verification.

  3. Step 3. Add the verification token to AI Plaza

    For HTML-tag verification, set NEXT_PUBLIC_GOOGLE_SITE_VERIFICATION to the content value Google shows, then redeploy. Alternatively upload the googleXXXX.html file into web/public/.

  4. Step 4. Submit the sitemap

    In Search Console → Sitemaps, submit https://aiplaza.app/sitemap.xml and wait for Success.

  5. Step 5. Request indexing for key URLs

    Use URL Inspection on / , /pricing, /docs, /tools, and /blog — about 10 requests per day. Do not mass-submit every tool page.

Get indexed on Google (Search Console)

For site owners who want Google to discover https://aiplaza.app. The product already publishes /robots.txt and /sitemap.xml. Search Console is the ownership and monitoring step.

You need a Google login to finish verification. Engineers can only paste the token or HTML file after you create the property.

Site files already live

Private areas (/account, /admin, /api/, sign-in) are disallowed in robots.

Step 1 — Create the property

  1. Open Google Search Console.
  2. Click Add property.
  3. Prefer Domainaiplaza.app (covers apex + www if used).
  4. Or use URL prefixhttps://aiplaza.app.

Step 2 — Verify ownership (pick one)

A) HTML meta tag (recommended with Vercel)

  1. In Search Console, choose HTML tag verification.
  2. Copy only the content value (a long token), not the whole <meta> tag.
  3. Set production env: NEXT_PUBLIC_GOOGLE_SITE_VERIFICATION=paste_token_here
  4. Redeploy, then confirm the homepage HTML includes the meta tag.
  5. Click Verify in Search Console.

B) HTML file upload

  1. Download googleXXXX.html from Search Console.
  2. Place it at web/public/googleXXXX.html.
  3. Deploy, then click Verify.

C) DNS TXT (Domain property)

  1. Copy the TXT record Google shows.
  2. Add it at your DNS provider for aiplaza.app.
  3. Wait for DNS propagation, then Verify.

Step 3 — Submit the sitemap

  1. Search Console → Sitemaps.
  2. Submit: https://aiplaza.app/sitemap.xml
  3. Wait until status is Success.

Step 4 — Request indexing (priority pages only)

Use URL InspectionRequest indexing for:

  1. https://aiplaza.app/
  2. https://aiplaza.app/pricing
  3. https://aiplaza.app/docs
  4. https://aiplaza.app/tools
  5. https://aiplaza.app/blog
  6. https://aiplaza.app/docs/getting-started-with-ai-plaza

There is a small daily quota. Do not burn it on every /tools/{id} page — the sitemap covers those.

Step 5 — Monitor

Watch Coverage / Pages, Sitemaps, and Performance once traffic starts.

Related

Frequently asked questions

How long until Google indexes AI Plaza?
Timing varies. After verification and a successful sitemap, the homepage often appears within days to a couple of weeks; broader indexing and rankings can take longer.
Where is the AI Plaza sitemap?
https://aiplaza.app/sitemap.xml — it includes home, docs, blog, pricing, tools index, and every /tools/{id} landing page.
What env var does AI Plaza use for Google site verification?
NEXT_PUBLIC_GOOGLE_SITE_VERIFICATION. The root layout emits <meta name="google-site-verification" content="…"> when this variable is set.
Should I request indexing for every tool page?
No. Use the daily request quota on a few high-value URLs. Let the sitemap and internal links discover the rest.