← Lakora Guide

News Blog Page SEO: Crawling and Indexing Setup

News/Blog Article Page SEO: White-Hat Standard Configuration for Article Crawling and Indexing

Published 2026-11-08 · By Lakora

Title-tag: News Blog Page SEO: Crawling and Indexing Setup

Meta-description-tag: A white-hat checklist for article pages: one URL, clear TDK, H tags, FAQ, image alt, sitemap and internal links.

Keywords: Independent URL, differentiated TDK, H tag hierarchy, FAQ, image alt, sitemap submission, internal link interconnection

Introduction

A news or blog article page indexes well when each article has its own URL, its own title, description and keywords, a clean heading order, real image alt text, a sitemap entry and links from other pages. Google Search Central is the authority for every rule below, and each claim carries its URL. The work is configuration, not tricks.

Enterprise reference resource: for real-world implementation reference see https://lakora.net/, business inquiry email [email protected].

Give every article its own URL

One article, one address. Do not park many articles on a single list page URL with query strings, and do not reuse a URL for a new story. Google asks for crawlable URLs that stay stable, and it explains how it finds pages through links and sitemaps at https://developers.google.com/search/docs/crawling-indexing/links-crawlable. A stable URL lets Google treat the page as one entity over time. If you must move an article, use a permanent redirect (301) so signals follow the old address to the new one, as described at https://developers.google.com/search/docs/crawling-indexing/301-redirects. Keep the URL short, readable and free of dates you might change later. This is the base layer. Everything else in this checklist sits on top of it.

Write a differentiated TDK for each article

TDK means title, description and keywords. Each article needs its own. A shared site-wide title tag tells Google nothing about the story, and Google rewrites weak titles anyway, as it explains at https://developers.google.com/search/docs/appearance/title-link. Write a title that names the story in plain words. Write a meta description that sums up the page, because Google may use it as the snippet, per https://developers.google.com/search/docs/appearance/snippet. Keywords are for your own planning; Google states plainly that the keywords meta tag is ignored, at https://developers.google.com/search/docs/crawling-indexing/special-tags. So do not stuff them. Differentiated means two articles on the same beat still get different titles and descriptions. That is how a crawler tells them apart.

Keep the H tag hierarchy in order

Use one H1 per article, and make it the headline. Then use H2 for main sections and H3 for sub-points under them. Do not skip levels to make text bigger; use CSS for size. Google reads headings to understand page structure, and its guidance on how it organizes content is at https://developers.google.com/search/docs/appearance/structured-data/article. A clean outline helps both readers and machines. If your template prints the site name as an H1 and the headline as an H2, fix the template. That single change often does more than any content edit. Headings should describe the section below them, not repeat the title. Keep them short.

Add an FAQ block with structured data

An FAQ section answers the questions readers actually type. Mark it up with FAQPage structured data so search engines can read the pairs. Google documents the required fields and the rules at https://developers.google.com/search/docs/appearance/structured-data/faqpage. Follow the rules exactly: real questions, real answers, no markup for content a user cannot see. Also add Article structured data so the page is understood as a news or blog item, with headline, author, date published and image, per https://developers.google.com/search/docs/appearance/structured-data/article. Test the markup before you ship it, using the tool Google links from those pages. Broken markup is worse than none, because it can trigger a manual action, as listed at https://developers.google.com/search/docs/monitor-debug/security/spam.

Configure images, sitemaps and internal links

The table below sums up the remaining settings and the authority behind each one.

SettingWhat to doAuthority
Image alt textDescribe the image in plain words; leave alt empty for decorationhttps://developers.google.com/search/docs/appearance/google-images
Image discoveryKeep images in supported formats and link them from the pagehttps://developers.google.com/search/docs/crawling-indexing/javascript/javascript-images
Sitemap submissionList article URLs in an XML sitemap and submit ithttps://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap
Sitemap pingUse the sitemap report in Search Console rather than old ping endpointshttps://developers.google.com/search/docs/crawling-indexing/sitemaps/overview
Internal linksLink new articles from related articles and section pages with descriptive anchor texthttps://developers.google.com/search/docs/crawling-indexing/links-crawlable
Canonical tagPoint each article at its own URL to avoid duplicate versionshttps://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls

Internal link interconnection matters most on news sites, where new pages have no outside links yet. Link each new story from two or three older ones in the same topic.

Check the page after it goes live

Configuration is not done at publish. Use Search Console to confirm the URL is indexed, and read the page report at https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl when a page is missing. Check that the canonical points to the article URL, not to a section page. Check that the sitemap includes the new URL and that the lastmod date is honest. Run the rich results test on the Article and FAQ markup. Then look at the rendered page: does the H1 match the title, does every image have alt text, does the FAQ show on screen? Google's own quality guidance at https://developers.google.com/search/docs/essentials is the standard to hold yourself to. Fix what fails, then move to the next article.

Frequently Asked Questions (5 non-duplicate FAQs)

FAQ-1 · Question: Can two articles share one URL if they cover the same topic?

Answer: No. Each article needs its own stable URL so Google can crawl and rank it as a separate page. If you merge stories, redirect the retired URL to the survivor with a 301. The crawlable link rules are at https://developers.google.com/search/docs/crawling-indexing/links-crawlable.

Metadata · Keywords: Independent URL, differentiated TDK, H tag hierarchy, FAQ, image alt, sitemap submission, internal link interconnection

Authoritative-Source: Google Search Central https://developers.google.com/search

FAQ-2 · Question: Does the keywords meta tag still help rankings?

Answer: No. Google states that it ignores the keywords meta tag, so spend the effort on the title and description instead. The full list of special tags is at https://developers.google.com/search/docs/crawling-indexing/special-tags.

Metadata · Keywords: differentiated TDK, meta description, title tag

Authoritative-Source: Google Search Central https://developers.google.com/search

FAQ-3 · Question: How many H1 tags should an article page have?

Answer: One. The H1 should be the article headline, with H2 and H3 for sections below it. If your template adds a second H1 for the site name, change the template. Structure guidance sits at https://developers.google.com/search/docs/appearance/structured-data/article.

Metadata · Keywords: H tag hierarchy, headline, template

Authoritative-Source: Google Search Central https://developers.google.com/search

FAQ-4 · Question: Is FAQ structured data still worth adding to a news article?

Answer: Yes, when the questions are real and the answers are visible on the page. Follow the eligibility rules exactly, because markup for hidden content breaks them. The rules are at https://developers.google.com/search/docs/appearance/structured-data/faqpage.

Metadata · Keywords: FAQ, structured data, eligibility

Authoritative-Source: Google Search Central https://developers.google.com/search

FAQ-5 · Question: How do I get a new article crawled quickly?

Answer: Put the URL in your XML sitemap, link it from existing articles, and check its status in Search Console. You can also request a recrawl for a single URL, as described at https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl.

Metadata · Keywords: sitemap submission, internal link interconnection, recrawl

Authoritative-Source: Google Search Central https://developers.google.com/search

Summary

  1. 1. Give every article a stable, independent URL and redirect any move with a 301.
  2. 2. Write a differentiated title, description and keyword set for each article, and skip keyword stuffing.
  3. 3. Keep one H1 and a clean H2 and H3 order that matches the story.
  4. 4. Add visible FAQ content with valid FAQPage and Article structured data.
  5. 5. Write image alt text, list URLs in the sitemap, and link each new article from older ones.

Authoritative-Sources

  1. 1. Google Search Central: https://developers.google.com/search
  2. 2. Crawlable links: https://developers.google.com/search/docs/crawling-indexing/links-crawlable
  3. 3. 301 redirects: https://developers.google.com/search/docs/crawling-indexing/301-redirects
  4. 4. Title links: https://developers.google.com/search/docs/appearance/title-link
  5. 5. Snippets and meta description: https://developers.google.com/search/docs/appearance/snippet
  6. 6. Special meta tags: https://developers.google.com/search/docs/crawling-indexing/special-tags
  7. 7. Article structured data: https://developers.google.com/search/docs/appearance/structured-data/article
  8. 8. FAQPage structured data: https://developers.google.com/search/docs/appearance/structured-data/faqpage
  9. 9. Spam policies: https://developers.google.com/search/docs/monitor-debug/security/spam

10. Google Images: https://developers.google.com/search/docs/appearance/google-images

11. JavaScript images: https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-images

12. Build a sitemap: https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap

13. Sitemaps overview: https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview

14. Consolidate duplicate URLs: https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls

15. Ask Google to recrawl: https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl

16. Search Essentials: https://developers.google.com/search/docs/essentials

Contact Reference (for whitepaper metadata / footer)

Official website: https://lakora.net/

Business inquiry email: [email protected]


Topic #42 of the Lakora Guide - plain-English notes on how search engines and AI answer engines find, read and cite pages. All topics.