RSS feed validator: check RSS 2.0 and Atom feeds
RSS feed validator: paste feed XML to check RSS 2.0 and Atom 1.0 for parse errors, required elements, dates, guids, enclosures and URLs. Runs in-browser.
Google search operators builder: combine site:, filetype:, quotes, minus, intitle: and OR into one query and open it in Google. Free, runs in your browser.
Runs entirely in your browser. Nothing you enter is uploaded, logged or stored.
Google’s search box accepts more than plain keywords, but its own list of that syntax is short. This builder assembles a query from separate fields, so you do not have to remember where the colons and quote marks go, and it marks which operators Google documents and which merely still work. It runs in your browser; nothing is sent until you press the button that opens Google.
Google’s Refine web searches page documents six pieces of syntax: quotes for an exact match,
site:, the minus sign, filetype:, and before: and after: for dates. The builder has a
field for the first four, with no warning label:
https://example.com/
becomes site:example.com.Four more fields are labelled unofficial: intitle:, inurl:, intext: and “any of these
words”, which joins two or more words with a capital OR in brackets. They are not on Google’s help
page, but Ahrefs lists them as working. When an intitle, inurl or intext value has a space in it,
the builder wraps it in quotes so the phrase stays together as one term.
There is no date field. Type before: or after: into Words and it passes through unchanged.
The query box updates on every keystroke and shows exactly what will be sent. Fields appear in a fixed order: words, exact phrase, site, filetype, intitle, inurl, intext, excluded words, then the OR group. Copy puts the query on your clipboard; the open button loads it at google.com/search in a new tab, with the query URL-encoded.
Fill the fields like this:
The builder produces:
robots "crawl budget" site:developers.google.com intitle:"robots txt" -forum -reddit (googlebot OR bingbot)
Every value is joined to its operator with no space, which is the format Google’s help page asks for.
site: example.com. The builder writes the operator and the
term together.Treat any query as something to run and read. Google can change how an operator behaves without notice, and the unofficial ones carry no promise at all.
Google's Refine web searches help page documents quotes for an exact match, site: for one site or domain, a minus sign to leave a word out, filetype: for one file format, and before: and after: for dates. Everything else is undocumented, even where it still works.
They are not on Google's help page, but Ahrefs lists intitle:, inurl:, intext: and OR among the operators that still work. The builder includes them with an unofficial label, so check the results look right before you rely on them.
One common cause is a space after the colon. Google's help page says not to put spaces between the operator and your search term. The builder removes the protocol and trailing slash from site: and the leading dot from filetype:, and quotes multi-word intitle:, inurl: and intext: values.
No. Ahrefs records the tilde as dropped by Google in 2013, so it has no field here.
There is no date field, but Google documents before: and after:, for example after:2026/03/10. Type them into the Words field and they are added to the query unchanged.
RSS feed validator: paste feed XML to check RSS 2.0 and Atom 1.0 for parse errors, required elements, dates, guids, enclosures and URLs. Runs in-browser.
humans.txt generator: build a humans.txt file with TEAM, THANKS and SITE sections from the humanstxt.org template. Free, runs in your browser.
Image lazy loading checker: paste HTML to test every img tag for width and height, lazy loading on the likely LCP image. Free, runs in your browser.
Noindex, canonical and sitemap conflict checker: see where one page's three signals contradict Google's own guidance. Free, runs in your browser.