If you've ever tried to figure out what a competitor is publishing by clicking around their site for twenty minutes, you already know how slow that gets. Google search operators let you skip the clicking and ask Google directly: show me the pages on this domain that mention this topic, or that have this word in the title, or that were updated after this date. This guide walks you through a working set of Google search operators and which competitive research question each one answers. By the end, you'll have a repeatable way to run a handful of searches, spot the pages worth opening, and record what those pages actually say.
Site search operators for competitor research aren't a separate skill from the advanced search operators SEO teams already use to check their own pages. It's the same syntax, pointed at someone else's domain instead of yours. If you've ever used site: to check whether your own blog post got indexed, you already know most of what this guide covers. The difference here is the mindset: you're not auditing your own work, you're reading a competitor's public site the way Google sees it.
It's worth setting one thing straight before you start. These searches will not hand you a complete inventory of a competitor's site, their traffic, their rankings, or whether AI tools cite them. They find candidate pages on Google, and what you do with those pages is the real work.
Set the competitor's site boundary
Start every search with site: followed by the competitor's domain. This restricts results to that one site, so you're not wading through the whole web to find what one company published. Add a topic word connected to the question you're actually asking, like site:DOMAIN pricing tiers or site:DOMAIN content calendar.
If the competitor has a recognizable section of their site, like a blog or a docs area, you can narrow further with a path: site:DOMAIN/blog/ TOPIC. Start broad, at the domain level, before you tighten to a section, since a wrong guess about their URL structure just gets you zero results.
You'll know this step is done when the pages coming back genuinely belong to the competitor you meant to search, and you can tell which part of their site your next searches are going to cover.
A lot of people treat a site: search as a complete list of everything on that domain, and it isn't. Google has said plainly that site: results aren't necessarily exhaustive, especially on bigger sites, and a search without another term isn't sorted by importance either. Google's own explanation is that results are close to random, generally showing the shortest URL first. So a missing result doesn't prove a page doesn't exist, and a site: search on its own doesn't tell you a company's best pages.
Common mistake: treating site:DOMAIN as a page-count audit. It's a discovery query, not a census. Add the topic you're investigating, open the pages that come back, and treat what you find as a sample worth reading, not a full count.
Find pages that put your topic in the title
Once you've bounded the site, add intitle: to look for pages that put a specific word in their title: site:DOMAIN intitle:TOPIC. A page that titles itself around a subject is usually a page the competitor built specifically to own that topic, which makes it worth your attention.
For an exact phrase, wrap it in quotes inside the operator: site:DOMAIN intitle:"feature name". If you want two words both in the title, you can repeat the operator, site:DOMAIN intitle:word1 intitle:word2, or reach for allintitle:word1 word2 when the constraint itself, both words appearing in the title, is the actual question.
You're done here once you've opened the relevant results and written down their real page titles and what each page is actually about.
The mistake to avoid is assuming an intitle: hit means the page ranks well for that term. It doesn't tell you anything about ranking. It also doesn't mean every word you type after intitle: is restricted to the title, only the one immediately following it, unless you repeat the operator or use allintitle:. And Google's displayed title in the results can differ slightly from what's actually on the page, so open it before you quote it anywhere.
Locate page types through their web addresses
URLs often carry a label for the kind of page they are. Try site:DOMAIN inurl:pricing, site:DOMAIN inurl:comparison, or site:DOMAIN inurl:docs, picking whatever label fits how this particular competitor tends to name things. You can combine a URL cue with a content term too, like site:DOMAIN inurl:pricing enterprise.
You've finished this step once you've actually opened the pages and confirmed their role, not just read the address and assumed.
People often equate a path label with what's currently on the page, or decide a competitor has no pricing page because inurl:pricing returned nothing. Sites label the same kind of page differently, calling it /plans/ instead, or putting it somewhere with no obvious label at all. If your first guess comes back empty, try a plain topic term instead, or a different label. allinurl: exists for when several words need to appear in the address together, not as a way to make a query look more sophisticated.
Check exact wording and on-page language
Sometimes the question isn't which page, it's whether specific wording exists at all. Wrap a phrase in quotes and pair it with site:, like site:DOMAIN "our AI writes it for you", to check whether a competitor uses that exact positioning line or feature name anywhere on an indexed page. Use intext: when you want to confirm a word shows up in the body text rather than just being implied by the title or URL: site:DOMAIN intext:automated. allintext: extends this to several words at once.
If you suspect the competitor might phrase something two different ways, run both with an uppercase OR between them, site:DOMAIN "phrase one" OR "phrase two", then look at each result individually rather than trusting the combined count.
This step is done when you've opened the page and confirmed the wording and its context yourself. Record what you find only after you've actually read it.
Pro tip: don't turn a snippet match into a product claim without opening the page, and don't treat zero exact-phrase results as proof the underlying idea is absent from the site. Loosen the phrase, try a synonym, or drop the text restriction before you conclude anything. A minus sign, like site:DOMAIN TOPIC -careers, is useful only when an unrelated category, jobs listings being a common one, is crowding out what you actually want to see.
Look for public documents worth reading
If a PDF, whitepaper, or spec sheet might answer your question, add filetype: to the search: site:DOMAIN filetype:pdf pricing. Swap in another format only when it's actually relevant to what you're investigating. Google identifies a file's type either by its content-type header or its file extension, so this isn't purely a search for files that happen to end in .pdf.
Once you've opened the document and checked who published it and when, and pulled out only the claims it actually supports, you're done with this step.
The mistake here is assuming every document a company has is indexed, or treating an undated document as current. If filetype: comes back empty, that only tells you this particular query didn't surface a matching document, not that none exists.
Narrow results by date, carefully
Add after:2025-01-01 to a focused search when recency matters, or before:2025-01-01 to look further back, or combine both to bracket a window: site:DOMAIN TOPIC after:2025-01-01 before:2025-06-01. Google accepts a year or a specific date, written with hyphens or slashes.
You're finished once you've checked each result for a visible publication or update date on the page itself and can tell that date apart from the filter you searched with.
The important nuance is that Google describes after: and before: as filtering by when a page was last updated, not a guaranteed first-publish date. Its own byline date is an estimate, not a verified timestamp, so don't describe a result as definitely published after your cutoff. If a date-restricted search misses a page you know is relevant, drop the date filter and check the page's own history instead. Never use this operator to reconstruct a competitor's exact publishing calendar.
Combine operators without overconstraining the search
Once you're comfortable with each operator on its own, you'll want to stack a few together for a sharper question. A query like site:DOMAIN inurl:pricing "annual plan" after:2025-01-01 is really four separate constraints layered on top of each other: the domain, the URL label, the exact phrase, and the date window. Stacking constraints like this can get you to the answer faster when it works, but it also fails silently. Each added operator narrows the result set, and a query with four narrow filters can return zero results even when a relevant page exists, simply because one of the filters didn't match the way you expected.
The fix is the same one you'd use to debug any filter: relax the constraints one at a time, starting with the narrowest. Drop the date first, since after: and before: are the most likely to exclude a page that's relevant but wasn't updated in your chosen window. If that still comes back empty, drop the exact phrase and search for the underlying idea instead of the precise wording. Keep the domain restriction and the URL label until last, since those are usually the parts of the query you were most confident about to begin with. A query that returns nothing tells you that this specific combination of filters found nothing, not that the competitor doesn't have the page you're looking for.
Use the Advanced Search form if you'd rather not type the syntax
Google also offers an Advanced Search form with fields for exact wording, alternative words, exclusions, a specific site or domain, and where a term should appear (in the title, the text, or the address), plus file type and last-update controls. It builds the same query string you'd type by hand, just through a form instead of memorized operator syntax. If you're new to this or helping a teammate who doesn't want to learn operator syntax, point them there first. It produces the identical search, it's just a friendlier way to assemble it. Using the form instead of typing operators directly doesn't change what the results can and can't tell you: the same limits on completeness, ordering, and date accuracy apply either way.
Record what you found and hand it off
The last step isn't a search, it's a habit. For each page worth keeping, write a short note: the question you were answering, the query you used, the page's title, what type of page it is, what the page itself directly confirms, its visible date if it has one, and what's still unknown. If a promising query has several filters stacked on it, relax them one at a time, starting with the narrowest, so you can tell a real absence from a filtering artifact.
If you're also checking your own site's coverage of the same topic, run the same searches against your own domain and compare the two lists side by side. Treat both as leads to review, not as a finished measurement.
You'll know you're done when someone else on your team could take your note, run the same search, open the same page, and tell your observation apart from your interpretation of it.
Watch for the mistake of inferring traffic, search position, a complete page count, or an AI-citation win from operator results. None of those are things a Google search result can tell you. If you need to debug your own site's indexing, Search Console's URL Inspection is the reliable tool, but it only works on properties you control, not a competitor's.
Where this hands off to a bigger picture
Operator searches are good at surfacing candidate pages fast. They're not built for ongoing, side-by-side coverage tracking, and they were never going to tell you whether a competitor's page gets cited in an AI answer.
That's where DeepSmith's Content Map comes in. Once you've used operators to spot a few interesting pages, Content Map turns your site and your competitors' sites into one shared map of topics, so you can see coverage gaps (topics where you publish but a competitor publishes more) and untapped topics (where a competitor has something and you have nothing) as an ongoing view instead of a one-off manual search. It checks sitemaps every 24 hours, so new competitor pages fold in automatically instead of requiring you to rerun your operator searches by hand.
If the question is specifically about AI visibility, whether a competitor's page is actually getting cited when someone asks ChatGPT or Gemini a relevant question, that's a different measurement than anything a Google operator can give you. DeepSmith's AEO competitor citations view tracks exactly that: which competitor pages win citations for the prompts you're tracking, and on which platform. Once you've measured a real gap, either in coverage or in AI citations, Opportunity Agents in DeepSmith turn that gap into a set of content ideas with the supporting evidence attached, so the idea isn't just a hunch, it's backed by a specific data point you can point to.
None of this replaces the manual search habit in this guide. It picks up where the manual search runs out of runway, once you're trying to track this continuously instead of checking it once. If you want to see how that works with your own site and a competitor list, DeepSmith offers a 7-day free trial to explore it with real data.
What to do next
Pick one competitor and one question you actually need answered this week, maybe what their pricing page says, or whether they've published anything new on a topic you're planning. Run through the seven searches above against that one domain, keep your notes in one place, and resist the urge to turn this into a marathon session covering every competitor at once. A focused pass on one site tells you more than a shallow pass across ten.
Once the habit sticks, site search operators for competitor research become something you reach for the same way you'd check a rival's pricing page before a sales call, quick, specific, and done in a few minutes instead of a scheduled project. Treat it the same way you'd treat any other advanced search operators SEO habit: a small, repeatable check you run often, not a one-time audit you do once a year and forget.
