Article page has no author
article_no_authorShort answer
The article names no author — not in the structured data, not in the byline. Google's helpful-content guidance asks "who" is behind the content; an author with a name and a page of their own is the direct answer. Add a byline, an author page and author.name (ideally author.url) in the Article schema.
Why it matters
Experience, expertise, authoritativeness and trust are evaluated partly from what the page says about its author. Anonymous articles are common on scaled, low-effort sites, which is exactly the pattern the 2026 spam updates target. A real byline with a profile page costs little and is a standing signal.
How Glimana detects it
For article pages, the rule fires when no author is found in the Article structured data or in the markup (rel=author, byline patterns).
How to fix it
- Find the affected pages in Glimana. Open Issues › Article page has no author. Every affected page is a row; open one to see the evidence Glimana recorded for it (the measured value, the offending element or the target URL). The same list sits on the task card under Tasks, and the page's own detail view under Pages shows its full signals.
-
Apply the fix on your platform.
Make sure the theme shows the byline and the author archive is enabled; SEO plugins add
authorto the schema from the post author. Fill the author's profile (bio, photo, links).Blog articles have an author field; show it in the article template and include it in the JSON-LD.
"author": {"@type": "Person", "name": "…", "url": "https://…/authors/…"}in the Article JSON-LD; print the byline and link it. -
Publish and clear caches. Save and publish, then make sure the crawler will see the new version: WordPress — clear the page cache in your cache plugin and purge the CDN; Shopify — theme and content changes go live on save, but purge any CDN in front of the store; custom code — deploy and purge the edge cache. Check in a private window or with
curl -s https://your-domain/page | grep -i '<title\|canonical\|robots'that the live HTML has changed; Glimana reads what the server sends, not what your browser has cached. - Verify in Glimana. Open the task under Tasks and click Mark as done. The affected pages are queued for a verification crawl within a few hours, and the task closes when an author is present. If the check still fails, the task returns to New with a note; when it passes, the task is listed under Resolved technical issues on Impact reports. To check sooner, use Re-crawl affected pages on the issue.
How the fix is verified
Re-crawl; the task closes when an author is present.