PRIUTH
SEARCH VISIBILITY · SITE OWNERS
Verify a hostname, submit your XML sitemaps, and inspect the crawl state and indexed-document samples known to PRIUTH.
STEP 01
PRIUTH requires proof that you control the hostname before it accepts sitemap submissions or reveals that site's crawl details. This console currently verifies one hostname at a time.
Choose any one method below. Keep the token exactly as shown, then select Verify ownership.
Create a TXT record at your DNS provider. The record name must resolve to the exact hostname shown below. If the provider automatically appends your zone, enter only the relative name needed to produce that exact hostname.
Set this as the TXT value without adding quotation marks. Keep the priuth-site-verification= prefix.
After DNS publishes the record, select Verify ownership. DNS propagation depends on your provider and TTL; retry if the first check does not find it.
Publish a plain-text file at this path on your website:
The entire file should contain only this token:
Add this tag inside the <head> element on your homepage:
VERIFIED PROPERTY
Matching pages known to PRIUTH
Waiting to be processed
URLs currently claimed by the crawler
Robots or crawl policy blocked these
Failed or retry-exhausted frontier entries
To protect the shared free-tier index, each metric samples at most 100 rows per category. A value shown as 100+ means the sample reached its cap, not an exact total. These are PRIUTH's current records, not a guarantee of indexing or search ranking.
DISCOVERY
Submit a public HTTPS XML sitemap hosted on the verified hostname. PRIUTH checks its XML structure, then queues the sitemap for the crawler. A sitemap may be resubmitted; limits are 20 distinct sitemaps per hostname and 10 submission attempts per UTC day. Failed validation attempts count toward the daily attempt limit.
| Sitemap | Validation | Crawler state | Checked |
|---|---|---|---|
| Verify a property to inspect sitemaps. | |||
The crawler respects robots.txt, same-host URL rules, and low-volume crawl limits. Sitemap discovery is capped; successful submission does not guarantee every URL will be fetched or indexed.
HOW IT WORKS
After verification, PRIUTH issues a per-site access key and keeps it in this browser tab's session storage. To regain access in a later session, verify ownership again. PRIUTH stores only a hash of the key. The console does not require a password or an email account.