StoreBuilt’s review of Shopify’s blog author guidance makes an important distinction visible: the author selected in the admin and the name rendered by a customised theme are not always the same source. We check both before changing anything. Otherwise, a team can save the correct author and still publish an old or hard-coded byline on the storefront.
To change a Shopify blog author, start with the article record, then verify every place that displays attribution. For UK ecommerce publishers, this includes the article page, blog cards and any structured data generated by the theme or an app. This guide explains the implementation checks and editorial decisions. Its scenarios are illustrative rather than claims about a specific client’s publishing results.
In this guide
- Decide whose contribution the byline describes
- Change the article author in Shopify
- Find where the visible name comes from
- Choose a maintainable approach for guest contributors
- Align structured data with the visible article
- An illustrative specialist buying guide
- Review the archive before making bulk changes
- Make the release check specific
- StoreBuilt point of view
Decide whose contribution the byline describes
Agree the editorial credit before opening the theme editor. The person who uploads an article is not necessarily its author. A staff writer, an external specialist and an internal reviewer may have different responsibilities, and the published wording should describe those roles accurately.
Choose a consistent format for individual and team contributions. A named author can help readers understand relevant experience, while a truthful team byline may suit a collaboratively maintained buying guide. Neither choice justifies inventing a person, a qualification or a review that did not happen.
Record the decision in the content brief. Include the intended display name, any biography reference and the person responsible for future updates. This prevents a later administrator from replacing a valid credit simply because their own account appears in a dropdown. Attribution should follow the work, not whichever login saved the latest edit.
Change the article author in Shopify
Shopify’s blog post guidance places blog posts under Content. Open the intended article, review the Author setting in its organisation details, select the correct eligible person and save. Reopen the record to confirm the selection persisted before investigating the public page.
The native author selector uses eligible store staff. Shopify says POS-only staff and collaborators do not appear, and its guidance identifies the relevant blog and Home permissions when an expected staff member is missing. Check the current account and permission requirements instead of assuming every person who can contribute copy is available in the selector.
Treat access as a separate business decision. Do not create a broadly privileged account merely to obtain a display name. If the editorial model regularly includes external contributors, decide how attribution will be represented without granting unnecessary operational access. The implementation should follow the business’s access policy and the current capabilities of the chosen setup.
Find where the visible name comes from
Open the live article and compare its byline with the saved record. If they differ, identify the rendering source. A theme might use the article’s author, a custom field, an app block or a fixed text value. Changing the record will not reliably change text that comes from another source.
Shopify’s Liquid article reference documents the author property available to themes. That provides a useful starting point for a developer inspecting the template. The investigation should also include article cards and related-content components because they may use different snippets from the article page.
| Surface | What to inspect | Common inconsistency to resolve |
|---|---|---|
| Article header | Visible name and source field | Saved author differs from byline |
| Blog listing card | Card snippet or section settings | Card still shows an old name |
| Author biography | Name, role and destination link | Biography belongs to another person |
| Structured data | Article author output | Markup contradicts the visible credit |
| Mobile layout | Wrapping and link usability | Long names overlap nearby metadata |
Use a preview copy for theme changes and preserve the original implementation. Correcting attribution should not require a broad redesign. Make the smallest coherent change that allows all relevant surfaces to use the agreed source consistently, then verify the rendered result.
Choose a maintainable approach for guest contributors
If native staff-based attribution does not fit your publishing model, compare a supported app or a considered custom content model. Define the requirement first: display name only, biography, multiple contributors, reviewer credit or an archive of articles. These are different levels of complexity and should not all be commissioned by default.
A custom field can be useful when it has a clear owner and fallback behaviour. Decide what appears when the field is empty and how editors know it needs completion. Avoid a silent fallback that credits an unrelated staff member. The content team should be able to understand the system without reading theme code.
For an app, test the complete output and the maintenance implications. Establish whether it changes the underlying article data, the visible theme or both. Ask what happens if the app is removed and how existing articles retain their credit. StoreBuilt’s Shopify content architecture guide covers broader content modelling decisions beyond this specific byline problem.
Align structured data with the visible article
Inspect the rendered page’s structured data after changing attribution. If an Article or BlogPosting object is present, its author information should describe the same credited person or organisation that readers see. Identify which theme code or app generates it before making corrections, especially if multiple components emit overlapping markup.
Google’s Article structured data guidance describes author information and recommends a URL that identifies the author. Use a relevant, maintained destination when your implementation supports it. Do not create an empty profile page solely to populate a field or imply credentials that are absent from the visible content.
Validate the output, then read the page as a customer. Structured data does not turn an unsupported expertise claim into evidence, and a corrected byline does not guarantee a ranking change or search enhancement. The practical aim is consistent attribution that readers and systems can understand.
An illustrative specialist buying guide
Imagine a UK outdoor retailer publishing a boot-care guide written by a product specialist and uploaded by an ecommerce assistant. The native article record initially credits the assistant, while a custom article template displays a general team name. This is an illustrative scenario, not a reported StoreBuilt project.
The editorial owner first agrees that the specialist should receive the writing credit and that any review should be labelled separately if it actually occurred. The developer then maps the fields used by the article header, listing card and structured data. The team chooses a consistent approach instead of adding a third hard-coded name.
A second editor previews the article without seeing the implementation notes. They should be able to identify the author, understand the person’s relevant role and follow any biography link. The same check on the blog listing catches a card that might otherwise retain the assistant’s name after the article page has been corrected.
Review the archive before making bulk changes
Search for the affected name across the published archive and classify why it appears. Some articles may be correctly attributed, while others inherited an uploader’s identity or a fixed template value. A global replacement can erase legitimate historical credit if those situations are treated as identical.
Prepare a small mapping with article references, current credit, intended credit and the reason for the change. Have the editorial owner review ambiguous cases. Where responsibility has changed over time, distinguish original authorship from current maintenance or review. An update does not automatically transfer authorship to the person who corrected a link.
Pilot the change on a small, representative set. Include an individual author, a team-authored article and any guest contribution relevant to the implementation. Check the output before expanding the change. Keep enough of the previous values to reverse an incorrect mapping without reconstructing the archive from memory.
Make the release check specific
A successful admin save is one checkpoint. The release is complete when the right credit appears on the relevant public surfaces and remains correct in the supported editing workflow. Test a subsequent edit as well as the initial correction if an app or custom field is involved.
| Check | Expected result | Owner |
|---|---|---|
| Editorial approval | Credit reflects the actual contribution | Content lead |
| Saved record | Intended author or custom field persists | Editor |
| Article and cards | Same attribution model across templates | Theme implementer |
| Biography destination | Relevant page loads and identifies the contributor | Content lead |
| Structured data | Author output agrees with visible content | Technical reviewer |
| Future edit | Normal publishing does not overwrite the decision | Publishing owner |
Record the chosen source and fallback in a short publishing note. New editors should know where to change a name and which fields must agree. If the theme is later replaced, include attribution in the migration checks so the store does not quietly revert to an uploader-based byline across the archive.
StoreBuilt point of view
A byline is a statement about responsibility. Make that statement truthful, maintainable and consistent wherever the article appears. StoreBuilt’s Shopify SEO and AI search services can help connect the editorial model with templates and structured data when the current setup produces conflicting signals.