How to Structure Author Information on WordPress to Boost Google Rankings and AI Citations

TL;DR Author information on WordPress is not decoration. It is data that Google and AI models read to figure out who stands behind your content. Google encourages accurate bylines that link to author background, but "E-E-A-T itself isn't a specific ranking factor." It is a quality framework, not a single ranking signal. The key technical piece is ProfilePage structured data with a mainEntity Person, plus an Article.author that points to the author page. WordPress shows the bare minimum by default. You need to add a bio, photo, sameAs links and clean markup yourself. Markup alone does not guarantee AI citations. It works together with real expertise, freshness and content that matches the question. Measure the result in AI answers (Semly tracks Citation Quality, sources and Share of Voice), not only in rankings. Honest caveat: there is no proof that author schema alone lifts rankings or citations. It is a play for entity clarity and trust.

What WordPress author information actually does for Google and AI

Author information is everything that tells a reader and a machine who wrote a page: the byline, the author page, the bio, the photo, the links to other profiles, and the structured data behind them.

On WordPress, most of this lives in one place (the user profile) and gets displayed in a few others (the post byline, the author archive). Your job is to make those pieces consistent and readable.

Here is the honest part. Google says: "We strongly encourage adding accurate authorship information, such as bylines to content where readers might expect it." It also asks whether bylines lead to further information about the author and the areas they write about.

But Google is equally clear that "E-E-A-T itself isn't a specific ranking factor." E-E-A-T is a framework for judging quality, not a switch you flip. And there is no study showing that author schema alone moves rankings or AI citations. Research on millions of AI citations found that schema markup had no significant independent effect once content depth, domain and page age were controlled.

So treat author information as a trust and disambiguation play. It helps Google and AI models connect a name to a real entity with a track record. That is worth doing, but it is not a hack.

What to watch out for: do not sell this as a ranking trick. If you promise rankings, you will be wrong. If you promise clarity and trust, you will be right.

Before you start: what you need and when this approach fits

This approach fits blogs, multi-author sites, and any topic where readers expect a real person behind the words (health, finance, legal, technical advice). It also fits service and e-commerce sites that publish guides and want those guides cited by AI.

It does not fit every case. If your content is anonymous by design, or purely product pages with no editorial voice, skip the author layer and lean on Organization markup instead.

Resource checklist:

• Author details: real name, role, short bio, areas of expertise.
• A photo you have the right to publish.
• Profile links: LinkedIn, personal site, Wikidata, company page.
• Access to the WordPress admin (Users section) and to your theme or a plugin for templates.
• A way to add JSON-LD (your SEO plugin, a code snippet plugin, or the theme).

Decisions to make first:

• Who is the author of each piece? One name, not "the team."
• What do you show publicly? Full bio, short bio, or just credentials?
• Do you want author archives indexed, or only the author page?

You do not need many authors to start. One well-built author page beats ten empty ones.

Step 1: Fill in the WordPress author profile properly

Go to Users → Profile and fill in the fields that actually matter. WordPress stores this in the wp_users table and exposes it through the REST API at /wp/v2/users.

Keep the bio short and specific. One or two sentences with a real qualification beat a paragraph of adjectives. "Maria writes about WordPress performance and has shipped 40+ sites" is better than "passionate content expert."

What to watch out for: /wp-json/wp/v2/users is public by default and can be used to list your users. If you want author pages indexed but not a full user directory exposed, restrict or disable that endpoint.

Step 2: Build a real author page (not an empty archive)

By default, WordPress author archives are close to an empty canvas: a name and a list of posts. That is not a page a human or a model can learn from.

Classic themes: copy author.php (or create author-{nicename}.php) in a child theme. Use get_the_author_meta() to output the fields you filled in Step 1:

$bio = get_the_author_meta( 'description' );
$url = get_the_author_meta( 'user_url' );

Block themes: open the Site Editor and edit the author archive template. Add blocks for the avatar, bio, and post list. No code needed.

What a good author page includes:

• Name and role.
• Photo.
• Two or three sentences of bio with real credentials.
• Areas of expertise (topics they actually cover).
• Links to LinkedIn, personal site or Wikidata.
• A list of their articles.

This is the page you will point Article.author to. Make it worth the click.

Step 3: Add Person and ProfilePage structured data

Now give machines a clean, unambiguous description. Google supports ProfilePage structured data, and its valid use cases explicitly include "an author page on a news site" and "an 'About Me' page on a blog site."

ProfilePage requires mainEntity (the Person). Recommended properties:

• name and alternateName
• description (byline or credential)
• image
• sameAs (LinkedIn, Wikidata, company page)
• identifier
• dateCreated and dateModified

Then link your articles to it. On the article page, Article.author should point to the author's ProfilePage URL. Use JSON-LD, which Google recommends.

sameAs is the disambiguation workhorse. It tells the model that this Maria is the same Maria as the LinkedIn profile and the Wikidata entry. Without it, you are just a name.

You can also add reviewedBy on articles that get an expert check. It is a trust signal, not a rich-result feature, so do not expect a visual change in search.

What to watch out for: never mark up information that is not visible to the user. If the bio is not on the page, it should not be in the markup.

Step 4: Avoid duplicate and conflicting author markup

This is the most common technical trap. Your SEO plugin generates Article and Person nodes. Your theme adds its own. Now you have two authors, two images, and a confused parser.

How to diagnose it:

1. Open the page and view the source. Search for application/ld+json.
2. Count how many Person and Article blocks appear.
3. Run the page through a validator and look for duplicate or conflicting entities.

Where markup can come from:

• Your SEO plugin (Yoast, Rank Math, SEOPress).
• Your theme or a child theme.
• A schema plugin.
• Manual JSON-LD in a snippet.

Google's rule is simple: "supply fewer but complete and accurate recommended properties rather than trying to provide every possible recommended property with less complete, badly-formed, or inaccurate data."

So pick one source of truth. If the plugin handles Article and Person well, turn off the theme's version. If the theme is better, disable the plugin's author output. Do not run both.

What to watch out for: after disabling one source, re-check the page. Removing markup can break other rich results if the plugin was handling more than authors.

Step 5: Validate and check what Google sees

Before you publish, confirm the markup is clean.

Mini validation checklist:

• Rich Results Test shows no errors on the author page and on a sample article.
• mainEntity is present on the ProfilePage.
• Article.author points to the author page URL.
• No markup describes content that is not visible.
• No duplicate Person nodes.

Common error symptoms:

• Missing mainEntity: the page is not recognized as a profile page.
• Invisible content warnings: you marked up a bio that is not on the page.
• Conflict warnings: two sources are fighting over the same entity.

After you deploy, use URL Inspection in Search Console to confirm how Google sees the page. Remember that Google "does not guarantee that features that consume structured data will show up in search results." Clean markup is eligibility, not a promise.

Step 6: Measure whether it works in AI answers

Rankings are only half the picture. The real question is whether AI models cite you and describe you correctly.

This is where Semly fits. Semly is an AI visibility platform that tracks how ChatGPT, Gemini, Claude, Grok, Google AI and Perplexity describe and cite brands. It gives you daily reports on citations and sources, plus metrics like Citation Quality (1 to 5), Share of Voice and an AI Visibility Score. You can see the full breakdown of these metrics in the AI visibility measurement guide.

Use it to answer three practical questions:

• Is my author or brand being cited at all?
• Which sources do the models pull from?
• How does my citation quality compare to competitors?

Set realistic expectations. AI answers are volatile. Research on hundreds of thousands of answers found that 48% of cited URLs appeared only once, and ChatGPT and Google AI Mode reused only about a quarter of the previous day's sources. One good day is not a trend.

Semly's free AI visibility report at report.semly.ai is a good starting point. If you run WooCommerce, note that Semly offers a WordPress/WooCommerce integration on its Advanced plan, so you can connect the site to the measurement layer. You can also review your brand's position, sentiment and sources in the Semly AI analytics dashboard.

What to watch out for: do not judge results from a single prompt or a single day. Track over weeks.

Common mistakes and how to fix them

• Empty author archive. Symptom: a name and a post list. Fix: build the page from Step 2.
• Bio with no credentials. Symptom: "passionate writer." Fix: add a real qualification or area of expertise.
• No sameAs. Symptom: the author is just a name. Fix: add LinkedIn, Wikidata or a personal site.
• Duplicate markup. Symptom: two Person nodes. Fix: keep one source, disable the other.
• Marking up invisible content. Symptom: validator warnings. Fix: only mark up what users can see.
• Treating markup as a citation guarantee. Symptom: disappointment. Fix: pair markup with real expertise and prompt-aligned content.
• Stale dateModified. Symptom: outdated bios. Fix: refresh bios and update the date when you do.

What to do next

Once one author works, scale it. Add more authors with their own pages, and use reviewedBy for pieces that get an expert check. Connect your author entities to your Organization markup so the site and its people are linked.

Refresh bios and dateModified regularly. Freshness matters to AI models, and stale profiles undercut the trust you are building.

Decision tree: public author or organization?

• Readers expect a person (advice, health, finance, opinion)? Use a public author with a full profile.
• Content is purely product or brand-level? Use Organization and editorial expertise instead.
• Author must stay anonymous by policy? Use Organization and lean on editorial standards and cited sources.

Either way, measure the outcome. Run a free AI visibility report with Semly, then track Citation Quality and sources over time to see whether your author structure is actually helping AI describe and cite you.

FAQ

Does author information improve my Google rankings? Not directly. Google says E-E-A-T is not a specific ranking factor. Author information helps with clarity and trust, which supports quality signals.

Do I need to code to do this? No. You can fill the profile and build the author page in the Site Editor. JSON-LD can come from your SEO plugin. Code only helps if you want full control.

Will author schema get me cited by AI? Not on its own. Research found schema had no significant independent effect on citations. It works as a supporting signal alongside expertise, freshness and content that matches the question.

How long before I see results? Expect weeks, not days. AI answers are volatile, so track trends over time rather than single answers.