"Aim for 1–2% keyword density."

There is no target. There never was.

Density is a metric SEO tools invented to have a number to sell you. But if you want a checklist that replaces it with something real, here:

— Use the exact phrase in the title, first paragraph, and one H2. That's coverage, not density.
— Then write naturally and never count again.
— Add related terms a real expert uses — not synonyms, entities. Writing about title tags? Mention SERP, pixel width, truncation, CTR. That's the actual signal.
— Read it aloud. If you wince at the repetition, you're over the line a human cares about, and Google's language model cares about the same line.
— Delete any sentence whose only job is to fit the keyword in again.

That's the whole method. (The 1980s density formula assumes search engines count words like a freshman essay grader. They've used embeddings for years. You're optimizing for a robot that retired.)

"Add 1,000 words to every thin page."

Please no.

Padding a page that answers its question in 200 words just buries the answer. Here's the actual triage checklist for a "thin" page:

— First ask: does the query need a long answer? "What time zone is EST" doesn't. Leave it short and proud.
— Check intent against the SERP. If page-one results are all short, your padding will rank you below them, not above.
— If it genuinely lacks depth, add the next questions — the People Also Ask follow-ups — not filler around the same point.
— Merge, don't pad. Three overlapping thin pages on near-identical topics should be one strong page plus two redirects.
— Consider noindex for utility pages that exist for users, not search. Thin isn't a sin; thin-and-indexed-and-useless is.

Word count is an output, never a target. (That "2,400 words ranks best" stat is survivorship bias — competitive topics happen to need more words, so the winners are long. The length didn't win. The depth did.)

Noindexing thin pages instead of fixing them

"Lots of thin pages hurting the site? Noindex them."

Lazy, and often wrong.

Noindex makes a thin page invisible but it doesn't recover the value — and if those pages have inbound links or topical relevance, you just threw it away. The mistake is treating noindex as a content strategy rather than a last resort.

Here's what actually happens: ten thin pages on closely related subtopics noindexed = ten weak signals deleted. Merge those same ten into one comprehensive page with proper headers and you've built something that ranks for all ten clusters at once and consolidates whatever authority they had.

Fix: triage first. Genuinely valueless (expired, duplicate, tag archives)? Noindex or 301. Thin-but-relevant? Merge and redirect into a stronger page. Noindex is for pages that shouldn't exist, not for pages that aren't finished. (Hiding the mess is not the same as cleaning it.)

"Keep titles under 60 characters."

Under 60 what? Pixels, not characters.

Google truncates by rendered pixel width, around 580px, so a title full of W's and M's clips early and one full of i's and l's runs long. Here's the real check:

— Stop counting characters. Use a pixel-based SERP preview tool. "Williamsburg Mortgage Workshop" and "illinois title tips" are wildly different widths at the same character count.
— Put the load-bearing words in the first ~480px. Everything after that is a bonus, not a guarantee.
— Mobile truncates differently from desktop. Check both; most clicks are mobile.
— A truncated title isn't automatically bad — if the meaningful part shows, the trailing "..." can even add curiosity.
— Brand at the end is the first casualty of truncation. Decide on purpose whether you're okay losing it.

The character-count rule is a useful lie for beginners. (It's the SEO equivalent of "i before e" — right often enough to teach, wrong often enough to embarrass you.)

"Optimize the H1 first, it's the most important on-page signal."

Sorry.

The title tag and the H1 do different jobs and you're ranking them backwards. The title tag is what the SERP shows and what algorithms weight as the page's stated subject. The H1 is a body element Google treats as one heading among many — useful, not load-bearing.

So the comparison is about where attention goes. If you have an hour, it goes on the title: it's the headline in the auction, it drives the click, it carries the keyword that matters. The H1 should match intent and orient the reader, but a perfect H1 under a weak title is a nice frame around an empty room.

The "H1 is king" myth survives because tools flag missing H1s in red and missing keyword-in-title in nothing. Red dots aren't priority.

(And no, you don't get penalized for two H1s. That study you're quoting was about HTML4 outline semantics that browsers never implemented.)

На Anthropic, OpenAI, Google и SpaceXAI подали в суд из-за ИИ

В Калифорнии против ИИ-компаний подали антимонопольный иск: регулятору показалось подозрительным, что игроки синхронно призывают ограничить развитие нейросетей ради безопасности. Смысл спора в том, что инвестиции в ИИ уже обгоняют реальный прогресс, а бизнесу выгодны правила, которые защитят капитал. Вывод: быстрых прорывов ждать не стоит, лучше выжимать максимум из текущих инструментов.

➡️ Читайте на сайте: https://aff.top/blog/na-anthropic-openai-google-i-spacexai-podali-v-sud-iz-za-ii

🧠 Ещё больше инсайтов → в канале AFF.top

Google ads начал показывать расходы конкурентов

Google Ads запустил Peer Spending — инструмент, который сравнивает расходы аккаунта с рекламодателями из той же ниши без раскрытия чужих данных. Он показывает, тратите вы больше, меньше или примерно на уровне конкурентов на уровне кампаний и групп объявлений. Для арбитража это скорее ориентир по бенчмаркам, чем инструмент прямого усиления залива.

➡️ Читайте на сайте: https://aff.top/blog/google-ads-nachal-pokazyvat-raskhody-konkurentov

🧠 Ещё больше инсайтов → в канале AFF.top

Минфин РФ планирует выпустить собственный стейблкоин

Власти РФ обсуждают запуск рублёвого стейблкоина: сейчас решают, как его обеспечить, какие операции разрешить и будет ли на него спрос. Основной кейс — международные переводы, а не использование физлицами. Если проект доведут до запуска, он может стать частью новой криптоинфраструктуры и альтернативой токенам, привязанным к дружественным валютам.

➡️ Читайте на сайте: https://aff.top/blog/minfin-rf-planiruet-vypustit-sobstvennyi-steiblkoin

🧠 Ещё больше инсайтов → в канале AFF.top

"Just canonical the duplicate pages so they don't compete."

Depends what you actually want — and people reach for canonical when they need a different tool.

Three instruments, three jobs. rel=canonical is a hint that says "these are the same page, credit this one" — Google can and does ignore it. noindex is a directive that says "keep this out of the index" — obeyed, but the page still gets crawled. robots.txt Disallow says "don't crawl this" — but a disallowed URL can still get indexed if it's linked.

The classic blunder: noindex a page AND block it in robots.txt. Now Google can't crawl it, so it never sees the noindex, so the URL lingers in the index forever. The two cancel out.

So: near-duplicates that should consolidate equity — canonical. Pages that must vanish from results — noindex, and let them be crawled. Crawl-budget waste you never want fetched — robots.txt, and don't expect it to deindex anything.

(Canonical to a noindexed page is the other trap. You're pointing equity at a door you nailed shut.)

"Add FAQ schema to win rich results."

That ship sailed.

Google restricted FAQ rich snippets to authoritative gov/health sites in 2023. Bolting FAQPage markup onto your blog post wins you nothing in the SERP now. Here's the on-page playbook that still works:

— Write the actual Q&A in the visible page body, as real H2 questions with direct answers underneath.
— Answer in the first sentence, then elaborate. That front-loaded answer is what gets pulled into AI summaries and snippets.
— Use the literal question phrasing people search — "how long should a title tag be", not "Title Length Considerations."
— Keep each answer self-contained. A passage that makes sense lifted out of context is a passage that gets quoted.
— Skip the JSON-LD theater for FAQs. It's dead weight on most pages now.

The markup was never the point. (People cargo-culted the schema and forgot the actual answers were doing the work. Strip the schema, keep the answers, lose nothing.)