inemaSEO 6 — Professional: selling and delivering SEO + AI as a service people can trust|INEMA.CLUB-PRO

Lesson 7 · 17 min

Ethics, risk and written authorization

A client request can take down their entire site: a network of sites, a thousand articles, forced indexing. You need to refuse by name, explain the risk and offer the safe path. And before touching anything, get in writing what you are allowed to do. An SEO diagnosis reads the site the way a search engine does: it is not a pentest.

Start the lesson
A hand signs a one-page document on the table while another person watches.

In this lesson you will

  1. 1The tactics Google treats as spam, by name
  2. 2What to offer in place of each one
  3. 3What the written authorization needs to say
  4. 4Why an SEO diagnosis is not a pentest

Goal: refuse by name the tactics Google treats as spam, write the client's authorization and make it clear that an SEO diagnosis is not a pentest.

01From request to safe execution

Tap each block.

Click each block in the diagram to see what it does.

Refuse with a reason, offer the safe path and have everything in writing.

02The tactics and what to offer instead

Tap each step.

1. Scaled content

Five variations per keyword, a thousand articles, agents publishing 24 hours a day: this is what Google calls scaled content abuse.

"Humanizing" the text to pass an AI detector doesn't fix it: it aims at the wrong metric (Google evaluates usefulness) and it is paraphrasing at scale with intent to deceive.

At INEMA283 entries of 170 to 240 words, two of them with 47% of their vocabulary in common, published in a single commit. Of the 6 in the sample, 5 were never crawled.

03Written authorization template

A template to adapt. It is not legal advice: for a large contract, run it by a lawyer.

SEO service authorization
AUTHORIZATION — [client] authorizes [you/company] — [date]

1. SCOPE: SEO and AI visibility diagnosis and monitoring
   of the sites: [domain 1], [domain 2]. Nothing outside this list.
2. WHAT IS READ: public pages (the way a search engine reads them, with a pause between pages).
   NOT A PENTEST: no password testing, forms, intrusion or search for security flaws.
3. ACCESS (minimum):
   - Search Console and Bing Webmaster: read-only user, in the name of [you].
   - DNS/domain: only to verify ownership, done by [client] or in their presence.
   - No passwords by message. Credentials stay out of repositories and reports.
4. WHAT CAN BE CHANGED: [e.g.: titles, sitemap, robots.txt, approved new pages].
   Every publication goes through approval by [name].
5. PERSONAL DATA: reports use aggregated data from the dashboards; no data from
   visitors or end customers is collected or exposed (LGPD).
6. WILL NOT BE DONE: network of sites, buying links, paid indexer, Indexing API outside
   permitted use, scaled content without review.
7. VALIDITY: until [date]. It can be revoked at any time in writing;
   upon revocation, access is removed within [N] days.

Signatures: [client] · [you]
Table: request → I decline → I offer
REQUEST                         | WHY I DECLINE                        | WHAT I OFFER
1,000 AI articles               | scaled content (spam policy)         | a few pages with original data
5 sites linking to each other   | link scheme; manual action           | contextual links and real mentions
"forcing" indexing              | Indexing API only JobPosting/Broadcast | sitemap, Search Console, IndexNow
text that passes a detector     | aims at the wrong metric             | human review and original data
"example" testimonials          | fabricated trust signal              | only real numbers with a source

04Practice: the paperwork before the work

The two documents that go with every proposal.

E1 · Completed authorization

30 min

Fill in the authorization template for the client from lesson 4 (or for your own site, as client zero).

Done when: all 7 items are filled in, the domains are listed one by one, the access is read-only, and the phrase "not a pentest" is in item 2.

E2 · Request, refusal, offer

20 min

Build your own table with 5 requests you have heard or expect to hear, the reason for declining, and what you offer instead.

Done when: each row names the tactic (scaled content, link scheme, site reputation abuse, forced indexing or fabricated signal) and has an alternative you can actually deliver.

05Test what you learned

The explanation appears after your answer.

Question 1 of 4

The client wants to use the Google Indexing API to index their blog posts. What do you say?skill

06Takeaways

Refuse by nameScaled content, link scheme, site reputation abuse, forced indexing, fabricated signal.
In writing, beforehandScope, sites, minimal access, what can change, who approves, personal data, validity.
Not a pentestThe diagnosis reads like a search engine. Security is a different service.

To go further

Google spam policies (English)Quality checklist (16 items)Course 2 · Content: what not to doProfessional 2030: common base (risks, LGPD, and scope)
Previous lessonNext lesson