Reddit v. Perplexity filing claims that Perplexity and three data vacuums (SerpApi, Oxylabs, and AWMProxy) pulled Reddit content by scraping Google’s search results, sidestepping robots.txt. I am not a lawyer. I read filings the way I read IKEA manuals: with coffee, confusion, and a small sense of dread.
The eyebrow-raiser is this: Reddit says it posted content that only Google could crawl. Hours later, Perplexity’s answers included that content. If the timeline holds, the clean explanation is that someone scraped Google’s results and piped the information into an answer engine. That is how half the internet works, in a way. This post covers the plumbing and leaves the ethics aside.
What this tells you about AI search
AI search is a filter, and no magical omniscience sits behind it.
- AI engines do not crawl the entire web in real time.
- They start with what surfaces in Google and a shortlist of trusted sources.
- They then run their own retrieval, scoring, and answer assembly on top.
- Freshness and structure matter a lot. Think of tools laid out on a pegboard instead of dumped in a bucket: retrieval grabs the neat stuff first.
If Google can see you, AI answers can see you. If Google cannot, you are yelling into a pillow.
What they are actually scraping for
They pull parts of your page instead of reading it like a person. Think of a parts bin.
- Problem: the user’s pain or question.
- Solution: the short fix or answer.
- Entities: specific names for people, products, versions, places.
- Verbs: actions that map to intent, like install, compare, diagnose, buy, cancel.
- Attributes: specs, dates, prices, counts, requirements, limits.
- Adjectives: qualifiers like free, beta, on-prem, FDA cleared. They are nice to have but secondary.
Different systems weight these signals differently, and I do not have the exact math. A sensible assumption is that entities and attributes carry more weight than adjectives, verbs help route intent, and problem and solution frame the whole page.
Under the hood, plain English
The lawsuit points to the following likely workflow, which practitioners also see in the wild:
- Discovery: query or scrape Google to find fresh, high-ranking URLs.
- Ingestion: fetch pages and split them into chunks.
- Embedding: turn chunks into vectors to compare against queries.
- Scoring: rank chunks by semantic match, structure quality, source credibility, and freshness.
- Answering: assemble a response and attach citations.
Some of you might think, “So authority still matters?” Yes. Credible mentions and clean references help. They are consistent signals that machines can verify.
How to write so AI systems actually pull your page
This part is under your control, and it needs good mechanics instead of hacks.
1) Lead with the answer
Put the problem and solution at the top, before any paragraphs about the future of innovation.
- Problem: “Widget X fails to connect after firmware 2.4.”
- Solution: “Update to 2.4.1 and reset pairing. Works for most users.”
Why it works: AI engines grab the first clean answer they find. Google’s helpful content approach also rewards direct, clear answers.
2) Name entities precisely
Use canonical names, models, versions, and regions.
- “Acme Widget X, firmware 2.4.1, Model AX-200, North America.”
Why it works: engines match pages to queries by entity. Reducing ambiguity increases retrieval accuracy.
3) Label actions with intent verbs
Use headers like Install, Configure, Troubleshoot, Compare, Buy, Cancel, and Migrate.
Why it works: systems route user intent to matching sections. Clear verbs make the right chunk easy to fetch.
4) List attributes cleanly
Use bullets or a small table, and include numbers.
- Version: 2.4.1
- Release date: 2025-10-12
- Works with: AX-200, AX-210
- Time to fix: 5 minutes
Why it works: attributes ground the entity. Google and AI both prefer concrete facts over hand-waving.
5) Add a mini-FAQ
Q and A pairs map to how people search and how AI answers.
- Q: Does this require admin rights?
A: Yes. Local admin or MDM approval. - Q: Does it work offline?
A: No. It needs an active connection the first time.
Why it works: FAQs create tidy retrieval targets and support rich results.
6) Stamp freshness
“Updated: 2025-11-03. What changed: added fix for 2.4.1.”
Why it works: recency raises visibility. A date plus a change note signals active maintenance.
7) Cite primary sources
Link to docs, standards, or original data. One solid source carries more weight than ten fluff blogs.
Why it works: citations reinforce trust. Google and AI both check the company you keep.
I have a few regrets in life. Letting pages sit stale for eight months is right up there with buying an elliptical I used twice.
Quick example you can steal
Title: Fix Widget X Connection Failures After Firmware 2.4
Updated: 2025-11-03
Problem: Widget X disconnects after updating to firmware 2.4.
Solution: Update to 2.4.1, reset pairing, and reboot the hub.
Key entities: Acme Widget X, firmware 2.4.1, Hub H-3
Attributes: Affected models AX-200 and AX-210. Fix time 5 minutes. Internal success rate 80 percent.
Diagnose
- Check firmware version in Settings.
- Confirm the hub is on H-3 or later.
Step-by-step fix
- Download firmware 2.4.1.
- Install update, then reset pairing.
- Reboot hub and test connection.
Alternative workaround
- Disable auto-sleep until 2.4.2 is available.
FAQ
- Q: Does this require admin rights?
A: Yes. - Q: Will this reset saved profiles?
A: No.
Common objections, straight answers
“Is AI search just piggybacking on Google?”
Mostly. Discovery flows through Google’s results, then AI applies its own layers.
“Do I need a brand-new strategy?”
No. Write for humans and structure for machines. Use the same topics with clearer framing and steady updates.
“Do adjectives matter?”
A little. They help with qualifiers like free trial or on-prem, but they do not outweigh entities and attributes.
Bottom line
Here is the punch list, and it lines up with my Treasure Map Entity SEO approach:
- State the problem and solution at the top
Why: AI pulls the first clear fix. Google’s helpful content approach favors fast answers. I follow the same rhythm: intent first, then the solution. - Name entities precisely
Why: engines match by entity. Canonical names, models, versions, and regions reduce confusion and raise match quality. That is Treasure Map 101: lock the entity, then expand the graph. - Use intent verbs in headers
Why: Install, compare, diagnose, and buy tie your sections to user tasks. Retrieval then grabs the right chunk without guessing. - List attributes in tight bullets or a small table
Why: specs, dates, counts, and limits anchor your entity and give AI stable facts to cite. Google rewards concrete details. - Add a mini FAQ
Why: Q and A mirrors query patterns and creates clean, reusable answer units. - Stamp freshness with dates and what changed
Why: recency raises visibility, and change notes signal ongoing care, which both Google and answer engines notice. - Cite primary sources
Why: credible references build entity trust and make it safer for AI to cite you.
This is the overlap that works: build clear entities, answer intent fast, structure content cleanly, and keep pages current. That approach is Google-friendly and comes straight from the Treasure Map teaching.
Want the deeper dive into my system? Join the course here: https://mastercoursereviews.com/
Then join the Facebook group SEO Training Camp for real-time feedback and hands-on entity mapping.
None of this is rocket science. Say the problem, show the fix, name the right things, and keep the page tidy. Then both Google and AI know what you are talking about. Skip these steps and you duct-tape your content to the wind.