Google search operators I still use after 20 years as a publisher

I have spent more than 20 years building and running publishing websites that live or die by search. For much of that time, Google itself was one of my SEO tools.

Before dashboards became the default answer to every question, I would use site: to look through an unwieldy archive, put a sentence in quotation marks to find copied content, or combine intitle: and after: to see how a competitor was covering a subject.

I still use Google search operators today. Not because they can replace Search Console, a proper crawler or a good SEO platform. They cannot. I use them because the answer to a small publishing question is often one carefully written query away, and opening three different tools would take longer.

This is therefore not a museum containing every command Google has ever recognized. It is a practical list of the Google search operators I have found useful as a publisher, how I use them, and where I no longer trust the answers.

The Google search operators I still find useful

1. site: — search one website rather than the entire web

The site: operator is the one I have used most often. It restricts results to a particular domain, subdomain, directory or URL.

site:searchenginewatch.com "Google Trends"

For a publisher, this is a quick way to find what an archive already contains. I use it before commissioning or writing an article, particularly when a website has changed ownership, content systems or editorial teams over the years. A normal WordPress search may miss an old article, while Google can surface the page immediately.

It can also reveal page types I did not expect to see:

site:example.com inurl:tag
site:example.com inurl:author
site:example.com filetype:pdf

What I do not do is treat the number above the results as an accurate count of indexed pages. Google explicitly says search operators are limited by its indexing and retrieval systems. If I need to diagnose the indexation of a particular URL, I use URL Inspection in Search Console. If I need a complete site inventory, I use a crawler and the site’s own database or sitemaps.

site: is a useful flashlight. It is not an indexation report.

2. Quotation marks — find an exact phrase

Putting a phrase inside quotation marks asks Google to search for that exact wording.

"Search moves fast. We watch it for you."

I have used exact-match searches for editorial research, quotation checking and finding an article that I remember by one sentence rather than by its title.

It is also one of the simplest ways to look for copied or syndicated content. Take a distinctive sentence from the article and exclude your own website:

"a distinctive sentence from the article" -site:example.com

This will not catch a heavily rewritten copy, and it is not a substitute for a full plagiarism-monitoring service. But for a fast spot check, it remains remarkably useful.

3. - — remove the results I do not want

The minus sign excludes a word, phrase or website from the results. There must be no space between the minus sign and the item being excluded.

seo conference -jobs -course

I use it when a query has been taken over by one meaning, one format or a few very large websites. It is particularly helpful during editorial research because it lets me remove results I have already reviewed and see what sits underneath them.

You can exclude an entire domain:

"best SEO tools" -site:reddit.com -site:youtube.com

Or remove your own site while looking for external brand mentions:

"Search Engine Watch" -site:searchenginewatch.com

The operator does not make the remaining results better by itself. It simply clears away a known source of noise.

4. intitle: — find pages deliberately focused on a subject

intitle: asks Google to return pages containing a word or phrase in the title.

site:searchenginewatch.com intitle:"Google Search Console"

This is more useful to me than a broad search when I want to see which articles were intentionally built around a topic. A phrase mentioned in passing inside an article is different from a page carrying it in the headline.

I use this operator when checking an archive before assigning new content, researching how competitors frame a topic and spotting several pages that may be chasing the same intent.

There is also an allintitle: variation, which asks for all the following words to appear in the title:

allintitle:google search operators

I regard that as a discovery shortcut, not a keyword difficulty score. The displayed result count is too approximate to tell me how hard a query will be to rank for. Ranking difficulty depends on the actual pages, websites, intent and SERP composition, not one large number returned by an operator.

5. inurl: — find particular sections and page types

inurl: limits results to pages with a word or phrase in the URL.

site:example.com inurl:reviews

Publishers tend to accumulate recognizable URL patterns: /reviews/, /author/, /tag/, /category/, /news/ and sometimes the remains of older content systems. inurl: lets me isolate one of those patterns without crawling the entire website.

It is also helpful in competitor research:

site:competitor.com inurl:review "SEO tool"

As with intitle:, I use allinurl: much less frequently. Adding more constraints can make a query look precise while quietly excluding useful results. I generally begin with one inurl: condition and only narrow it further if the result set is still noisy.

6. intext: — find a term inside the page itself

intext: looks for a word or phrase in the body of a page rather than relying on the title or URL.

site:searchenginewatch.com intext:"internal linking"

One practical use is finding possible internal-link opportunities. If I am working on a priority page, I can search the rest of the site for pages that already discuss its subject:

site:example.com intext:"target topic" -inurl:target-page

The query does not tell me whether the phrase is already linked, where it appears or whether the surrounding paragraph is still relevant. I still have to open the result and exercise editorial judgment. What it does is produce a shortlist in seconds.

7. filetype: — find original reports, presentations and documents

filetype: restricts results to a particular kind of file. PDF is the obvious example, but Google can surface several other document formats.

"search quality" filetype:pdf site:google.com

For publishers, this is one of the most useful research operators because it can lead past articles summarizing a study and directly to the study itself. I use it to find research papers, company reports, regulatory documents, conference presentations and older material buried inside institutional websites.

It can also reveal files from your own website that Google has indexed:

site:example.com filetype:pdf

That matters if a report was supposed to sit behind a form, an obsolete media kit is still discoverable or an old PDF contains information the editorial team has since corrected.

8. before: and after: — narrow results by date

These operators are useful individually or together:

site:searchenginewatch.com "Google Trends" before:2020-01-01

site:competitor.com "AI search" after:2026-01-01

site:competitor.com "SEO tools" after:2026-01-01 before:2026-07-01

I use them to separate historical coverage from recent coverage, reconstruct how a topic developed and review what a publication produced during a particular period.

There is an important limitation. The date Google associates with a document is not always its original publication date. A substantial update, structured data, sitemap information or other signals may affect the date Google understands. I use these operators to narrow research, not to establish a definitive publishing chronology.

9. OR — search several names or versions of an idea

OR tells Google that either term can satisfy the query. It should be written in uppercase.

"generative engine optimization" OR "AI search optimization"

This is helpful in an industry that regularly invents several names for the same or overlapping ideas. It also works well for products that have changed names, companies that have rebranded and people whose names are written in different ways.

For larger queries, I group alternatives inside parentheses:

("generative engine optimization" OR "answer engine optimization" OR "AI search optimization") site:example.com

Grouping becomes especially useful when I combine alternatives with another condition or exclusion. It keeps a complicated research query readable enough that I still understand what I asked Google to do.

10. * — leave a blank inside a phrase

The asterisk acts as a wildcard. It is most useful inside quotation marks when I know the shape of a phrase but not every word inside it.

"best * tools for publishers"

I have found this useful for language and title research. It can reveal the words people and publishers place between two known parts of a phrase.

I would not use wildcard results as quantitative keyword research. Google may interpret broad searches more flexibly than the syntax suggests, and the results can vary. I use the asterisk to discover wording and possibilities, then validate anything important elsewhere.

11. imagesize: and src: — two useful operators for Google Images

These are more specialized, but they are relevant to publishers managing large image libraries. Both work in Google Images rather than ordinary web search.

imagesize: finds pages containing an image with specified dimensions:

site:example.com imagesize:1200x675

This can help locate images produced for a particular template or identify undersized assets that may need replacing.

src: searches for pages referencing a particular image URL in their HTML:

src:https://example.com/wp-content/uploads/example-image.jpg

It can be useful when investigating where a hosted image appears. It will not discover every copied image, especially when someone has downloaded, renamed or resized the file, but it gives publishers another quick way to trace direct reuse.

Five operator combinations I return to most often

Individual operators are easy to remember. The combinations are where they become genuinely useful.

1. Search a large editorial archive for existing coverage

   site:example.com "target topic"

2. Find possible internal-link opportunities

   site:example.com intext:"target topic" -inurl:target-page

3. Look for copied or syndicated sentences

   "distinctive sentence from the article" -site:example.com

4. Review a competitor’s recent coverage of a subject

   site:competitor.com intitle:"target topic" after:2026-01-01

5. Find primary documents instead of articles discussing them

   "target topic" filetype:pdf site:.gov

These are not elaborate SEO tricks. That is precisely why they have lasted. Each answers a narrow question quickly.

Google search operators I no longer use or trust

Some commands disappeared. Others still produce results but not ones I would build a decision around.

• cache: no longer works. Google removed its documentation in September 2024 and explicitly confirmed that the operator had stopped functioning.
• link: is not a backlink checker. Even when it produced results, it never offered the completeness needed for serious link analysis.
• related: has been too inconsistent for me to treat it as a dependable way of identifying competitors or similar publications.
• daterange: required Julian dates and was never worth the friction. before: and after: are clearer.
• inanchor: and allinanchor: may appear in old lists, but I would use a dedicated backlink index rather than base link research on them.
• allintitle: result counts should not be presented as keyword difficulty. The query can help surface competing pages, but the headline number is not a serious competition metric.
• The result count from site: should not be reported as the number of pages Google has indexed. Search Console and a proper technical review are better suited to that job.

This is one problem with enormous search-operator lists: retired and unreliable commands can remain in circulation long after their practical value has gone.

Google’s current search guidance highlights quotation marks, site:, the minus sign, before:, after: and filetype: among its popular operators. Google also warns that operators are constrained by indexing and retrieval limits.