Drupal SEO checker: diagnose URLs and metadata

A Drupal SEO check should sample a current alias, its node path, a taxonomy term, and a translated pair. This exposes differences between content records, module settings, and anonymous public output.

Compare the alias with the internal node route

Request both addresses and record statuses, final destinations, and canonicals. If both serve content, investigate implemented redirect and canonical behavior before deleting an alias. For a path changed by Pathauto, follow an old link too: a functioning new alias does not establish that the previous one redirects correctly.

Inspect a content-type-specific pattern

Compare an article and a service page for titles, descriptions, and robots directives. When a missing description affects only one type, investigate that type's field mapping or fallback. Sample a sparse taxonomy page to see whether the sitemap advertises it despite offering little context. Do not disable an entire SEO module to repair a configuration limited to one bundle.

Request both languages anonymously

Load Vietnamese and English URLs without administrative cookies. Confirm publication, language-appropriate content, self-canonicals, and reciprocal language links. If behavior changes after login, inspect access permissions and relevant cache contexts. Following a fix, retest alias and node routes plus another translated page sharing the template. Record cache-clearing time so an older response is not confused with a remaining configuration defect. External crawling cannot reveal every internal permission or cached variation.

A worked publishing scenario

Illustrative scenario: administrators see the latest node while the public alias returns older content. Compare cookie-free requests, publication permissions, and cache output after the edit. Request another node of the same type plus a translation of the original. Keep the results associated with their exact routes and access contexts. Do not delete the alias to conceal the symptom before identifying whether routing, permissions, or cached responses caused it. After correction, repeat each access path so a working administrative session is not mistaken for a public fix.

Run a check and interpret the evidence

Submit one representative public URL to the free SEO checker below. Record its status, title, description, and canonical alongside the exact address and time of the check. Group repeated issues by their responsible template or configuration so a single targeted fix can be retested on multiple pages. A missing field and an intentional exclusion need different decisions.

An HTTP/HTML audit observes public responses. It does not sign into the platform, inspect every administrative setting, reproduce every client-side rendering behavior, or prove that Google has indexed a page. For search-engine evidence, compare Search Console URL Inspection and subsequent crawl data. Recheck the original URL after publication and cache refresh instead of interpreting a changed score alone as proof that the underlying issue is resolved.

Tools and related guidance

• Read the Drupal configuration guide
• Check a public URL
• Inspect a redirect chain

Official references

• Drupal: Pathauto
• Drupal: Pathauto and Redirect