Show who wrote your posts
Add a named author with their role and a short bio, so Google and AI tools trust your posts. See where each site shows it, and the "last updated" date.
Last checked against the product on
Google and AI assistants trust a post more when it's written by a real, named person who knows the subject: an accountant writing about VAT, a plumber writing about boilers. Telling Blog AI who writes for your site puts that name, with what qualifies them, on your posts.
Blog AI only uses what you write here. It never makes up a name, a job title or a qualification.
Add your site's author
- Open the site's settings. On the Sites page, open Author on the site's card.
- Write the author's name, for example "Jane Murphy".
- Add their role or qualifications (optional), for example "Chartered accountant (ACCA), 15 years advising small firms".
- Add a short bio (optional, up to 300 characters): one or two sentences about their experience.
- Add a profile link (optional): your About page or their LinkedIn. It must start with https://.
- WordPress: choose who to publish as. Pick the WordPress user that posts should go out under. Blog AI lists the users your site already has and never creates one.
- Click Save.
Every post on that site now shows this author, unless the post has its own (below).
A different author for one post
Open the post and find Author in the side panel. Tick A different author for this post and fill in the same fields, then click Save author. Untick it to go back to the site's author.
"Reviewed by"
If someone with the right expertise checked a post, for example a dietitian checking a nutrition post, add their name and role under Reviewed by on the post. It's optional, and it's sent only where your site has a place for it (below).
Where the author shows up
When a post is published, or the whole post is updated, Blog AI sends the author to your site where it has somewhere to put it:
| Your site | What Blog AI does with the author |
|---|---|
| WordPress | Publishes as the user you chose. If a user has the same name as the post's author, that user is used. Publishing as someone else needs an Editor or Administrator connection; otherwise the post goes out under the connected user and Blog AI tells you. |
| Strapi | Fills the author field you mapped under Fix connection: as text, or the linked author entry with the author's name (else the one you picked for every post). "Reviewed by" and an "Updated date" field can be mapped too. |
| Webhook | Sends the author (name, role, bio and link) and "reviewed by" with every post. |
Each site's Author section says what happens on that site.
Blog AI never creates users, authors or author entries on your site. Update live post and refreshes change the post's text only: a new author reaches your site the next time you publish or update the whole post.
Dates: "Last updated"
When a refresh, a rewrite, a merge or Update live post changes the text of a live post, Blog AI records the date. The original publish date never changes.
- WordPress updates its own "last modified" date by itself.
- Strapi gets the date in the "Updated date" field you mapped, if you mapped one.
- Webhooks get it as
updated_at.
Search engines read this date to see that a post is kept up to date. Your theme decides whether readers see it.
Next step
Next stepPublish or schedule a postPublish a post to WordPress or Strapi now, or schedule it. How scheduling differs between the two, what happens if it fails, and read-only sites.More about this part of Blog AI: Publishing and scheduling.
Related articles
- Update a post that is already liveSend edits to a published post with “Update live post”. The web address never changes, and Blog AI won’t overwrite edits made on your site.
- Refresh a post that is losing trafficStart a refresh, review the proposed changes section by section, and apply the ones you accept to your live post without changing its address.
Was this article helpful?
Still stuck?
Tell us what you were trying to do and what happened, and we'll reply by email. Contact us.