Use a robots meta tag in server-rendered or static head markup whenever possible.
SEO & search
Build a robots meta tag without conflicting directives.
Choose what compatible crawlers may index, follow, and preview. Get clean markup plus a plain-English review before adding it to the page head.
- Runs in your browser
- Source-linked guidance
- No visibility guarantee
Choose crawler instructions
Build the tag.
Use robots unless you intentionally need a Google-specific instruction.
Runs entirely in your browser. No settings are sent or stored.
Review before publishing
Generated meta tag
Defaults selected. No robots meta tag is needed.
No robots meta tag is needed for these defaults.
Indexing and following are the normal default behavior.
What these settings mean
- Indexing is allowed, but inclusion in search results is never guaranteed.
- The crawler may follow links from this page under its normal policies.
Before you paste it
- The crawler must be allowed to fetch the page before it can discover this tag.
- Check for existing meta tags and X-Robots-Tag headers; restrictions can combine.
- Use an X-Robots-Tag response header for PDFs and other non-HTML files.
- Robots directives are not privacy, authentication, or access controls.
Use it with context
A directive is guidance—not an access control.
Put the generated tag in the HTML head and make sure the crawler can fetch the page. If robots.txt blocks that URL, the crawler cannot discover a noindex instruction there. Changes also depend on a later recrawl, so removal is not immediate.
Use an X-Robots-Tag HTTP response header because those files have no HTML head.
Why no noarchive option?
Google now documents noarchive, nocache, and nositelinkssearchbox as historical rules it no longer uses. This builder does not present them as current Google controls. Other engines may support different rules.
Primary sources
Guidance you can verify.
Reviewed August 22, 2026. Search-engine behavior can change, so the builder links the rules back to current documentation.