2,184 addresses. 1,000 duplicates. One public API key. viberrr caught them.
Palm Reading Near Me lists palm readers in 50 states and 120 cities. Nobody can click through a site that size by hand. viberrr read every address in its sitemap, went straight to its busiest pages, and found what was hiding there.
The site: Palm Reading Near Me, a directory of 2,128 palm readers with ratings and review counts from Google. Every number here can be checked: palmreadingnearme.com.
8195
Out of 100, across 13 checks for search, AI answers and agents.
2,1842,311
Before: 1,000 duplicate addresses, and 1,128 reader pages missing. Now every one of the 2,128 readers is listed once.
590
The Chicago page. Photos now load through the site's own server.
A thousand pages is a normal day.
A directory, a store or a docs site grows faster than anyone can review it. viberrr doesn't sample the home page and guess. On this site it:
No setup beyond the site's address. The same checks run again on a schedule, so a duplicate section or a leaked key that ships next month gets caught next month, not next year.
Same reader, two addresses, a thousand times over.
One reader as search engines found it, before and after.
Before
Palm Reading Near Me · Oct 27, before
81visibility score
/reader/moon-over-medium-st-louis
/palm-readers/missouri/st-louis/moon-over-medium-st-louis
Same reader, two addresses. × 1,000
One address per page: fail. 1,000 pages listed twice; no page names its real address.
What viberrr's check found
- One address per page1,000 duplicates
- No keys exposed on deeper pages59 on one page
- Images that loadFail
- Structured data that says what it isNeeds work
- Readable by AI, sitemap, titlesPass
After
with viberrrPalm Reading Near Me · Oct 27, after
81visibility score
/reader/moon-over-medium-st-louis → 308
/palm-readers/missouri/st-louis/moon-over-medium-st-louis
One reader, one address.
One address per page. Every page names its real address; the sitemap lists each once.
viberrr's check, re-run on the live site
- One address per pagePass
- No keys exposed on deeper pages0 found
- Images that loadPlaceholders for now
- Structured data that says what it isPass
- Readable by AI, sitemap, titlesPass
Found by the checks, fixed in one change.
- Oct 27
viberrr reads the whole site map
Palm Reading Near Me is a directory: 2,128 reader profiles across 50 states and 120 cities. viberrr read all 2,184 addresses in its sitemap and compared them. One address per page: fail. “1,000 pages appear in your sitemap under two different paths, so search engines see duplicates and split their attention.” None of the pages said which copy was the real one.
- Oct 27
It follows the site down to its busiest pages
Problems on a big site hide deep, not on the home page. viberrr worked out which city pages hold the most listings and checked those. On Brooklyn and Chicago it found a Google Maps Platform key inside every photo link, 59 times on the Chicago page alone, readable by anyone. A key like that can run up the owner's bill. The same pass found the photos themselves no longer loading.
- Oct 27
The fixes, in one change
The 1,000 duplicate addresses now permanently redirect to the real pages, and the sitemap lists each page once. Every page names its one real address. Reader pages tell search engines what they are (a local business, with its city and phone). And photos now load through the site's own server, so the key never reaches a browser.
- Oct 27
viberrr re-checks the live site
Same checks, same site, the same day: the score went from 81 to 95, the 1,000 duplicate addresses left the sitemap, and the key from 59 copies on the Chicago page to none. The security check no longer finds it anywhere it looks.
- Oct 27
One more find, and a new check
While making these fixes, the owner's agent noticed the site had 2,128 readers but the sitemap listed only 1,000 of them: the database hands back 1,000 rows at a time, and the sitemap asked once. 1,128 reader pages existed but search engines were never told about them. The fix reads every row, and the sitemap now lists all 2,128. viberrr now checks every site for this, and the new check catches this site's before-state.
Big sites break quietly.
When every page has a twin, search engines have to guess which one to rank, and they spread their attention across both. Nothing looks wrong in a browser: both copies work. It only shows up when something reads the whole site and compares.
An API key in a page is the same kind of problem. The home page was clean; the key only appeared on the city pages, deep in the data the page loads. Checking where the listings actually are is how it got found before someone else found it.
Rankings take weeks. We'll show you either way.
Search engines have to recrawl 1,000 redirects and settle on the real pages before traffic moves. We'll add Search Console numbers to this page at 30 and 90 days, whatever they show.
Published Oct 27, 2026. No traffic results yet.
Still on the list, from the same checks
- Bring the reader photos back: turn the photo service back on in Google Cloud with a new, restricted key.
- Retire the old key everywhere it's stored.
- Add a named author to the guide pages.
- Publish an agent card, so other agents know what the directory does.
How big is your site?
Add it to viberrr and the same checks read the whole thing: every address in the sitemap, the busiest pages first, with the fix for anything that fails.