How Do You Add Author and Reviewer Credentials to a Webflow Blog?

My posts have a byline. Why is that not enough?

Because a name is not a credential. A byline tells a reader who typed the words. It does not tell them why that person is worth believing on this topic, and it gives a machine almost nothing to connect your author to anything else on the web. The gap between those two things is where most blogs lose trust.

This walkthrough is for one specific situation: you run a Webflow blog, you have somewhere between one and five people writing, and you want author and reviewer credentials that a reader can act on and a machine can read. If you have a newsroom with a standards editor, you need something bigger than this. If you are a solo consultant, this is exactly your size.

I will go in the order I actually build it, because doing the template before the fields is how people end up redoing this twice.

What does Google actually say about author information?

More than most people realize, and it is specific. Its guidance on creating helpful content states that of the aspects it groups as E-E-A-T, meaning experience, expertise, authoritativeness and trustworthiness, trust is most important, and that the others contribute to trust without every piece of content needing to show all of them.

The same page asks two questions that read like a checklist for exactly this job. "Do pages carry a byline, where one might be expected?" and "Do bylines lead to further information about the author or authors involved, giving background about them and the areas they write about?" Its self-assessment list also asks whether content is written or reviewed by someone who demonstrably knows the topic.

Read that second question again, because it is the one almost nobody satisfies. A byline that links nowhere passes the first test and fails the second. The deliverable is not a name. It is a name that leads somewhere real.

Which fields do you need before touching the template?

Four on the author, and two on the post. On the author you want the person's name exactly as it should appear, a short biography written in plain language, one canonical profile URL that you control or that is clearly theirs, and the topic areas they are actually qualified on. That is it. Resist adding more.

On the post you want a reference to the author, and a separate optional reference to a reviewer. Keeping those as two distinct fields is the whole trick, because it lets you say that one person wrote something and a different person checked it, which is a far stronger claim than either alone.

Webflow's CMS supports a Reference field that points at another collection, which is what makes this clean rather than copied. I can confirm the field type from the live schema of the collection this blog runs on, where the category field is a Reference into a separate Categories collection. The same mechanism carries authors.

How do you set up the Authors collection?

Create a collection for people, with one item per human, and give it the name, biography, profile URL and topic fields. Then add the two Reference fields on your posts collection pointing at it. Check Webflow University for the current Designer steps, since the interface moves and I would rather you follow their screenshots than my memory of them.

The thing I would insist on is one item per real person, never a generic "Editorial Team" item. A collective author is a placeholder that will still be there in two years, and it fails the test of leading somewhere real. If nobody is willing to put their name on a post, that is useful information about the post.

Bind the author fields into the post template so the biography and the profile link render on every article, not only on a separate author page. A reader deciding whether to trust a claim is on the article, and sending them hunting through your site to find out who wrote it is a step most of them will not take.

What goes in the bio, and what does not?

What makes the person credible on this topic, stated plainly, in two or three sentences. Years doing the work, the kind of work, and anything checkable. My own reads that I am a Certified Webflow Partner who has delivered more than seventy projects for over twenty-five clients across six years, because each of those is a thing someone could challenge.

What does not go in is adjectives. "Passionate about digital experiences" is not a credential and a reader has learned to skip it. Neither is a list of every tool the person has ever opened. The bio is doing one job, which is answering why this person rather than anyone else, and anything that does not serve that job is making the answer harder to find.

An unexpected background is worth including rather than hiding. Mine is aeronautical engineering, which has nothing obvious to do with websites, and it is more memorable and more human than another sentence about results. Specific and slightly odd beats polished and interchangeable.

How do you add a reviewer without pretending to have a newsroom?

Be literal about what the reviewer did. If someone checked the technical claims, the label is that they reviewed the technical claims, with their name and the date. Do not write "fact checked" unless somebody checked every fact, and do not invent a review process you do not run. An honest narrow claim is stronger than a vague broad one.

For a solo practice the honest version may be that there is no second reviewer, and that is fine. In that case say what you do instead. I state that I verify claims against primary sources before publishing, which is a real process I can describe, rather than implying an editorial board that does not exist.

Where a reviewer genuinely adds weight is on anything outside your own expertise. If you write about a legal or medical angle and someone qualified read it, that is exactly the situation the reviewer field exists for, and it is worth the effort of asking.

What does the Article markup need to say?

Google's Article guidance is blunt about the author name. It says to specify only the name of the author in the author.name property and to add no other piece of information, which rules out the publisher name, a job title, an honorific, and introductory words like "posted by".

A lot of templates get this wrong by concatenating a title into the name. It also says to use the Person type for people and the Organization type for organizations, and strongly recommends including the type and url, or sameAs, properties so Google can better understand who the author is. That url is why the canonical profile field earns its place in your collection.

And it says to make sure that all the authors presented as authors on the web page are also included in the markup. So if your visible byline credits two people, your markup credits two people. Your JSON-LD and your visible page are making the same claim or they are making a mess. I went deeper on the markup itself in my piece on author schema and sameAs for blog posts.

How do you check it worked?

Three checks. View the rendered page and confirm the author name, bio and profile link are actually there in the HTML. Run the page through Google's Rich Results Test and the Schema Markup Validator. Then open the page in a private window as a stranger and ask whether you could tell who wrote it in five seconds.

On the first check, what you are looking for is that the credential is in the HTML rather than injected by a script after load. The third check is the one people skip and it catches the most. Markup can validate perfectly while the visible page buries the author in a footer at eight pixels. The markup helps a machine. The visible credential is what persuades the human who is deciding whether to believe you, and both have to work.

Spot-check more than one post, and specifically check an old one. Author fields added to a template apply everywhere, but older items often have the reference field empty, which renders as a byline with nothing behind it on exactly the posts that have accumulated the most links.

What quietly undoes all of this?

Stuffing the author name field. Someone adds "Pravin Kumar, Certified Webflow Partner" to the name because it looks authoritative on the page, and now the markup is doing the thing Google's documentation explicitly says not to do. Credentials belong in the bio and the profile link, not in the name.

The second is a profile URL that rots. If you point sameAs at a platform profile you do not control and later abandon that platform, you have a credential leading to a dead end. I would always include a page on your own domain as the primary one, and treat an external profile like LinkedIn as the secondary.

The third is scope drift. You list five topic areas on an author because it feels stronger, then that author writes about something on the list they have never actually done. The topic list is a promise about where this person is credible, and padding it is the fastest way to make the whole apparatus look decorative. Topical honesty and topical authority are closer than they look.

What should you do next?

Build the Authors collection with those four fields, add the author and reviewer references to your posts, and bind them into the article template. That is an afternoon of work for a small blog. Then write one honest bio for yourself, with something checkable in it, and use it as the standard for everyone else.

After that, run the old-post check. Every article published before the fields existed needs an author assigned, and that backfill is boring and genuinely matters, because those are the pages with history behind them. If you run a multi-author setup, my walkthrough on setting up a multi-author blog in Webflow covers the structure in more detail.

If you want someone to look at whether your author setup is actually doing anything, or to build it properly once rather than three times, reach out. It is a small job with an unusually long shelf life.