Skip to content

docs(lens): exact_matches works now — stop saying NOT YET SUPPORTED (SCR-180) #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
0xGhostCasper merged 1 commit into from
Oct 5, 2026
Merged

docs(lens): exact_matches works now — stop saying NOT YET SUPPORTED (SCR-180) #53

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions src/scrapebadger/google/lens.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,12 +64,13 @@ async def search(
visual_matches: Visual matches are the only surface this
endpoint serves, so they are always returned. ``False``
is echoed in ``warnings``.
exact_matches: NOT YET SUPPORTED. Accepted for API
compatibility and echoed in ``warnings``. Google renders
its Exact-matches tab client-side and ScrapeBadger cannot
reach it yet, so the response is the full match grid —
it CONTAINS the pages hosting the same image, but Google
does not label which ones those are.
exact_matches: Return just the pages hosting this image,
each flagged ``exact_match``, instead of the broad visual
grid — what a copyright or provenance check needs. Google
exposes this set for most images but not all (6-7 of 10
in our sampling); when it is unavailable the full grid is
returned and ``warnings`` says the filter was not
applied, so you never have to guess which you got.

The response carries a ``warnings`` list naming every parameter
that could not be applied. Check it rather than assuming a filter
Expand Down
Loading