{"id":1046,"date":"2026-08-11T20:18:18","date_gmt":"2026-08-11T20:18:18","guid":{"rendered":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/"},"modified":"2026-08-11T20:18:18","modified_gmt":"2026-08-11T20:18:18","slug":"how-to-change-a-google-docs-template-without-breaking-your-content-workflow","status":"publish","type":"post","link":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/","title":{"rendered":"How to Change a Google Docs Template Without Breaking Your Content Workflow"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A shared Google Docs content template becomes a workflow control when writers, editors, SEO managers, approvers, and publishers use it for the same client work. Changing that template can therefore affect more than spacing or typography. A renamed field, removed approval checkpoint, or changed heading rule may alter what information is collected and how the next person interprets it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For an agency, <strong>Google Docs change template<\/strong> work should be handled as workflow versioning. The goal is not simply to make a cleaner document. It is to preserve the fields, ownership, approval evidence, and CMS handoff requirements that active production depends on.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This guide covers how to decide between an in-place revision and a new version, audit the current fields, build a role-controlled replacement, migrate active work safely, and validate an approved document in a CMS draft before general rollout.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why changing a Google Docs template can disrupt an agency publishing workflow<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><img decoding=\"async\" src=\"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/08\/1b5f5c94d5.webp\" alt=\"Flow from a Google Docs template through drafting and editorial approval to a CMS draft and scheduled release.\">\n<em>A template supports a sequence of drafting, editorial approval, CMS handoff, and controlled release.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A content template is used at several points in the production path. The team may use it to collect the brief, write the article, record SEO requirements, document review status, and prepare information for a CMS handoff. A change to one section can therefore create a gap at a later stage.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Document the intended sequence explicitly:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>A writer creates or updates a draft using the approved template version.<\/li>\n\n\n\n<li>An editor checks the article, metadata, links, images, and client requirements.<\/li>\n\n\n\n<li>An approver confirms the current version and records the decision.<\/li>\n\n\n\n<li>A publishing operator transfers the approved content to a CMS draft.<\/li>\n\n\n\n<li>The team checks the CMS draft before scheduling or releasing it.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Consider the operational effect of these changes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If the <strong>meta title<\/strong> field is removed, the team must identify where that value is now stored and who verifies it.<\/li>\n\n\n\n<li>If a clear <strong>featured-image instruction<\/strong> becomes a vague note, the asset owner or publisher may not know whether an image is approved, pending, or required.<\/li>\n\n\n\n<li>If the <strong>client approval status<\/strong> is deleted, the workflow needs another explicit way to distinguish editorial completion from client or account approval.<\/li>\n\n\n\n<li>If the template allows both manually bolded section titles and heading styles, the team should define which convention controls the final hierarchy.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These are not automatic failures in every agency. They are breakpoints to test before rollout. If the replacement makes a required decision harder to find, changes who completes it, or removes the condition that blocks an incomplete handoff, editors and publishers will have to resolve that ambiguity elsewhere.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The practical boundary is to treat Google Docs as the collaborative source and the CMS as the destination record. The template should identify what the source contains, which version was approved, and what the publishing operator must verify in the destination. For broader source-to-CMS workflow guidance, see the site\u2019s <a href=\"https:\/\/wp001.tenwrite.com\/google-docs-writer-workflow-for-agencies-from-client-draft-to-wordpress-ready-content\">Google Docs writer workflow for agencies<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Decide whether to revise the existing template or create a new version<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><img decoding=\"async\" src=\"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/08\/87a8cdc2b4.webp\" alt=\"Decision tree for choosing between revising an existing Google Docs template and creating a new version.\">\n<em>Use an in-place revision for unchanged workflow meaning; version structural or mapping changes.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Before changing a shared master, determine whether the change affects only presentation or changes the meaning of the workflow. This decision matters because existing documents do not automatically acquire new fields or instructions when a master template changes.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Change<\/th><th>Recommended action<\/th><th>Reason<\/th><th>Completion condition<\/th><\/tr><\/thead><tbody><tr><td>Correct a spelling error or clarify wording without changing the requirement<\/td><td>Revise in place<\/td><td>The field and decision rule remain the same<\/td><td>The owner records the change and confirms active documents remain interpretable<\/td><\/tr><tr><td>Add examples to an existing instruction<\/td><td>Usually revise in place<\/td><td>The example explains an existing requirement<\/td><td>An editor confirms it does not introduce a new obligation<\/td><\/tr><tr><td>Add, remove, or rename a required field<\/td><td>Create a new version<\/td><td>Active documents may lack information needed later<\/td><td>The new version has a field map and cutover date<\/td><\/tr><tr><td>Change the heading structure or required content sections<\/td><td>Create a new version<\/td><td>Writers and editors may otherwise use incompatible structures<\/td><td>A representative article passes editorial and CMS checks<\/td><\/tr><tr><td>Add a client-specific requirement<\/td><td>Create a scoped or client-specific version<\/td><td>The requirement may not apply to other accounts<\/td><td>Scope, owner, and affected assignments are documented<\/td><\/tr><tr><td>Change how a field maps to the CMS<\/td><td>Create a new version and run a handoff test<\/td><td>The destination may require a different value or location<\/td><td>Each affected field has a destination and validation rule<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Use this decision rule: <strong>revise in place when the document still means the same thing; create a new version when required information, ownership, structure, or destination mapping changes.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the team cannot confidently determine whether active documents still mean the same thing, use a new version. A practical name might be <code>Client Blog Article \u2014 v2 \u2014 Effective 2026-09-01<\/code>. The name is useful only if the team also records the changes, scope, and effective date.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Audit the current template\u2019s required content and publishing fields<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before building a replacement, inventory the fields production actually uses. Review the document body, header, instructions, comments, status labels, and any linked brief or publishing record. The purpose is to identify what must remain available for editorial QA and CMS handoff.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create a field inventory with four decisions: <strong>keep, remove, rename, or add<\/strong>. Include the owner, destination, and completion rule for every retained or new field.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field or section<\/th><th>Current state<\/th><th>Decision<\/th><th>Owner<\/th><th>Completion rule<\/th><\/tr><\/thead><tbody><tr><td>Document title<\/td><td>Article title appears at the top<\/td><td>Keep<\/td><td>Writer<\/td><td>Matches the approved working or CMS title<\/td><\/tr><tr><td>Client and site identifier<\/td><td>Present in the header<\/td><td>Keep<\/td><td>Writer or account lead<\/td><td>Names the client, site, and relevant post type<\/td><\/tr><tr><td>Content type<\/td><td>Not always consistent<\/td><td>Add or standardize<\/td><td>Editor<\/td><td>Identifies the approved post, page, or other type<\/td><\/tr><tr><td>Target URL or slug<\/td><td>Included in some briefs<\/td><td>Keep<\/td><td>SEO manager or editor<\/td><td>Has no unresolved placeholder and follows the client rule<\/td><\/tr><tr><td>Primary topic or keyword<\/td><td>Present<\/td><td>Keep<\/td><td>SEO manager or writer<\/td><td>Identifies the intended search topic<\/td><\/tr><tr><td>Meta title<\/td><td>Free-text note<\/td><td>Rename and clarify<\/td><td>SEO manager or editor<\/td><td>Is written, reviewed, and ready for the destination field<\/td><\/tr><tr><td>Meta description<\/td><td>Present<\/td><td>Keep<\/td><td>SEO manager or editor<\/td><td>Is written and checked before approval<\/td><\/tr><tr><td>Categories and tags<\/td><td>Mixed into article notes<\/td><td>Move to CMS field block<\/td><td>Editor or publisher<\/td><td>Uses approved terms for the target site<\/td><\/tr><tr><td>Featured-image brief<\/td><td>Unclear<\/td><td>Rename and clarify<\/td><td>Writer, editor, or asset owner<\/td><td>States asset status and required caption or alt-text information<\/td><\/tr><tr><td>Internal-link requirements<\/td><td>Present in comments<\/td><td>Move to checklist<\/td><td>Writer and editor<\/td><td>Required links are present and checked<\/td><\/tr><tr><td>Writer status<\/td><td>Inconsistent labels<\/td><td>Standardize<\/td><td>Writer<\/td><td>Shows in progress, ready for edit, or returned<\/td><\/tr><tr><td>Editor status<\/td><td>Present<\/td><td>Keep and define<\/td><td>Editor<\/td><td>Cannot be approved while required checks are incomplete<\/td><\/tr><tr><td>Approver<\/td><td>Sometimes recorded elsewhere<\/td><td>Add<\/td><td>Account lead or client owner<\/td><td>Names the decision-maker and approval date or timestamp<\/td><\/tr><tr><td>Target publish date<\/td><td>Present in a calendar only<\/td><td>Add or link clearly<\/td><td>Publisher or account lead<\/td><td>Includes date, time, time zone, and authorization<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">For every field marked <strong>remove<\/strong> or <strong>rename<\/strong>, answer three questions:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Where does the information go now?<\/li>\n\n\n\n<li>Who completes or verifies it?<\/li>\n\n\n\n<li>What stops the handoff if it is missing?<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">For example, changing <code>SEO notes<\/code> into separate <code>Meta title<\/code> and <code>Meta description<\/code> fields is incomplete if the editor does not know both are required or the publisher does not know where they belong. A label alone is not a control; the owner and pass condition make it operational.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Build the replacement template with clear writer and editor controls<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Build the replacement around decisions and handoffs rather than decoration. A person opening the document should be able to identify the client, article, current status, content requirements, and release decision without searching through unrelated comments.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use three broad sections.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Header block: shared project and publishing metadata<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Place these fields before the article body:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Client or brand<\/li>\n\n\n\n<li>Destination site<\/li>\n\n\n\n<li>Content type<\/li>\n\n\n\n<li>Working title<\/li>\n\n\n\n<li>Primary topic or keyword<\/li>\n\n\n\n<li>Target URL or slug<\/li>\n\n\n\n<li>Assigned writer<\/li>\n\n\n\n<li>Assigned editor<\/li>\n\n\n\n<li>Current template version<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The writer can complete the working title, topic, and draft details. The account or operations owner should confirm the destination site and content type. Include the template version in the master copy or document name so the team can identify which rules governed the draft.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Content body: writing and editorial requirements<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Define the required article structure, introduction, body sections, links, and image notes. Use the document\u2019s heading styles consistently instead of treating bold text or font size as a substitute for a heading instruction. The exact hierarchy should follow the client\u2019s content rules; the template\u2019s job is to state which hierarchy writers must use.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Keep instructions separate from final copy. A labeled note such as <code>Writer instruction: explain the reader\u2019s next action<\/code> is less ambiguous than an instruction embedded in a paragraph where a publisher could mistake it for article text.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Assign responsibilities explicitly:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Writer-owned:<\/strong> first draft, working title, primary topic, proposed slug, source links, internal-link opportunities, and image brief.<\/li>\n\n\n\n<li><strong>Editor-owned:<\/strong> factual and structural review, heading hierarchy, link checks, metadata review, taxonomy confirmation, and editor status.<\/li>\n\n\n\n<li><strong>Approver-owned:<\/strong> client or internal approval decision, approved version, approval date, and exceptions.<\/li>\n\n\n\n<li><strong>Publisher-owned:<\/strong> CMS destination, post type, final field mapping, draft creation, schedule, and release status.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Release block: approval and CMS handoff<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Place the release block after the article or in a clearly labeled document section. Include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Meta title<\/li>\n\n\n\n<li>Meta description<\/li>\n\n\n\n<li>Category and tags<\/li>\n\n\n\n<li>Excerpt, when required by the destination<\/li>\n\n\n\n<li>Featured-image status and alt-text requirement<\/li>\n\n\n\n<li>Final internal-link check<\/li>\n\n\n\n<li>Writer status<\/li>\n\n\n\n<li>Editor status<\/li>\n\n\n\n<li>Approver and approval date<\/li>\n\n\n\n<li>Target publish date, time, and time zone<\/li>\n\n\n\n<li>CMS handoff status<\/li>\n\n\n\n<li>Exception notes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Define completion conditions in the template. For example, <code>Editor status: Approved<\/code> should be available only after the article body, headings, links, image requirements, taxonomy, excerpt, and SEO fields have been checked. <code>CMS handoff: Draft created<\/code> should mean only that the destination draft exists; it should not authorize public release.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use this before-and-after field map when replacing an existing template:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Old template field<\/th><th>New template field<\/th><th>Owner<\/th><th>CMS or workflow destination<\/th><th>Required check<\/th><\/tr><\/thead><tbody><tr><td>SEO notes<\/td><td>Meta title and Meta description<\/td><td>SEO manager or editor<\/td><td>SEO fields<\/td><td>Both values are present and reviewed<\/td><\/tr><tr><td>Publishing notes<\/td><td>Category, tags, excerpt, and target post type<\/td><td>Editor or publisher<\/td><td>CMS taxonomy and post settings<\/td><td>Values match the client site<\/td><\/tr><tr><td>Image note<\/td><td>Featured-image brief and asset status<\/td><td>Writer, editor, or asset owner<\/td><td>Featured image and media review<\/td><td>Asset is approved or explicitly marked pending<\/td><\/tr><tr><td>Review complete<\/td><td>Editor status and approval record<\/td><td>Editor and approver<\/td><td>Workflow state<\/td><td>Current version and decision-maker are recorded<\/td><\/tr><tr><td>Publish date<\/td><td>Target date, time, and time zone<\/td><td>Publisher or account lead<\/td><td>Schedule settings<\/td><td>Release timing is authorized and unambiguous<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This map forces the team to decide what each new label controls. Every field should have an owner, destination, and pass condition.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Roll out the new version without mixing versions in active production<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Assign an owner and effective date before sharing the replacement. Do not rely on writers noticing an unexplained change to a shared document or assuming that an existing draft has been updated.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use this rollout sequence:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Name the replacement clearly.<\/strong> Include the client or scope, version number, and effective date.<\/li>\n\n\n\n<li><strong>Record the change.<\/strong> List each added, removed, renamed, or relocated field and the reason.<\/li>\n\n\n\n<li><strong>Set a cutover date.<\/strong> State when new assignments must use the replacement.<\/li>\n\n\n\n<li><strong>Classify active assignments.<\/strong> List which drafts remain on the old version and which may move to the new one.<\/li>\n\n\n\n<li><strong>Handle in-progress drafts explicitly.<\/strong> Keep them on the old version unless the editor or operations owner approves a migration. If migrating, duplicate the source, preserve the original, and record the new document version.<\/li>\n\n\n\n<li><strong>Update assignment links.<\/strong> New briefs and writer instructions should point to the correct version.<\/li>\n\n\n\n<li><strong>Name the question owner.<\/strong> Identify who resolves disputes about fields, status labels, or exceptions.<\/li>\n\n\n\n<li><strong>Archive the old master as read-only.<\/strong> Keep it available for active assignments and history, but remove it from the default path for new work after cutover.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Use two production lanes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>In-progress assignments:<\/strong> remain on the old version unless an explicit migration decision is recorded.<\/li>\n\n\n\n<li><strong>New assignments:<\/strong> use the replacement from the effective date onward.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Rollout passes when every active assignment has a known template version, every new assignment points to the replacement, and the retired master cannot be mistaken for the current one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Validate the template through an approved-document-to-CMS handoff test<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><img decoding=\"async\" src=\"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/08\/d76ae6e49b.webp\" alt=\"Checklist for validating an approved Google Docs document in a CMS draft before release.\">\n<em>Validate identity, structure, links, media, taxonomy, SEO fields, approval, and release state before rollout.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not approve a replacement based only on the blank document\u2019s appearance. Test a completed document using the new structure. Choose at least one representative article for each relevant content type or client configuration. Where practical, include both a normal article and a variation containing links, an image, taxonomy values, an excerpt, and SEO fields.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Run the test in this order:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Create a document from the new template.<\/li>\n\n\n\n<li>Populate every required field with representative content.<\/li>\n\n\n\n<li>Move the document through the intended writer and editor statuses.<\/li>\n\n\n\n<li>Record a named approval for the tested version.<\/li>\n\n\n\n<li>Send the approved document to the CMS as a draft, not directly to public release.<\/li>\n\n\n\n<li>Compare the source with the CMS draft field by field.<\/li>\n\n\n\n<li>Record defects, return the document to the responsible owner, and retest after correction.<\/li>\n\n\n\n<li>Approve the template for general use only after the required checks pass.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Use this pass\/fail checklist:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>[ ] <strong>Source identity \u2014 Pass:<\/strong> client, destination site, content type, document version, and approved source are recorded. <strong>Fail:<\/strong> the operator cannot identify which site or template rules apply.<\/li>\n\n\n\n<li>[ ] <strong>Article structure \u2014 Pass:<\/strong> title, headings, paragraphs, lists, and required sections appear in the CMS draft as intended. <strong>Fail:<\/strong> headings are flattened, skipped, or replaced by formatting that changes their meaning.<\/li>\n\n\n\n<li>[ ] <strong>Links \u2014 Pass:<\/strong> required internal and external links are present, relevant, and usable in the destination draft. <strong>Fail:<\/strong> a link is missing, points to the wrong destination, or remains an unresolved placeholder.<\/li>\n\n\n\n<li>[ ] <strong>Images \u2014 Pass:<\/strong> the featured image or image instruction reaches the correct media review step, with required caption or alt-text information. <strong>Fail:<\/strong> the asset is missing, unapproved, or assigned to the wrong content item.<\/li>\n\n\n\n<li>[ ] <strong>Taxonomy \u2014 Pass:<\/strong> category and tag values match the target site\u2019s approved terms. <strong>Fail:<\/strong> values are absent, ambiguous, or copied from another client profile.<\/li>\n\n\n\n<li>[ ] <strong>SEO fields \u2014 Pass:<\/strong> meta title and meta description are present in the intended destination fields and have been reviewed. <strong>Fail:<\/strong> either value is missing, unexpectedly truncated, or left in body copy instead of the CMS field.<\/li>\n\n\n\n<li>[ ] <strong>Excerpt \u2014 Pass:<\/strong> the approved excerpt is present when required by the content type. <strong>Fail:<\/strong> the CMS generates an unintended excerpt or the field is blank without an approved exception.<\/li>\n\n\n\n<li>[ ] <strong>Approval state \u2014 Pass:<\/strong> the approver, approved version, and approval date are recorded. <strong>Fail:<\/strong> the document is treated as ready because an editor marked it complete without a final approval decision.<\/li>\n\n\n\n<li>[ ] <strong>Release state \u2014 Pass:<\/strong> the CMS item remains a draft until scheduling or release is authorized. <strong>Fail:<\/strong> the test changes public content or creates an unexplained schedule.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This test checks more than formatting. It checks whether the revised template still carries the editorial and publishing decisions required at the destination. For the markup and conversion portion of the process, use the <a href=\"https:\/\/wp001.tenwrite.com\/google-docs-to-html-converter-a-clean-export-and-qa-workflow-for-content-teams\">Google Docs to HTML export and QA workflow<\/a> when that matches your handoff route.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tenwrite can fit after this approval boundary when the team needs to move approved Google Docs content into a CMS draft for review, scheduling, or release. Keep the CMS draft review and final release decision with the designated editorial or publishing owner.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Maintain template ownership and review it when workflow requirements change<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Assign one accountable owner to the master template. Writers and editors should be able to suggest improvements, but suggestions should be reviewed before the master changes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Keep a lightweight change log with these columns:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Version<\/th><th>Date<\/th><th>Change<\/th><th>Reason<\/th><th>Approver<\/th><\/tr><\/thead><tbody><tr><td>v1<\/td><td>Initial release date<\/td><td>Initial field structure<\/td><td>Define the article handoff<\/td><td>Operations owner<\/td><\/tr><tr><td>v2<\/td><td>Effective date<\/td><td>Split SEO notes into two fields<\/td><td>Make metadata checks explicit<\/td><td>Editorial and SEO owner<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Review the template when any of these triggers occurs:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A client adds or removes a publishing requirement.<\/li>\n\n\n\n<li>The CMS field structure or post type changes.<\/li>\n\n\n\n<li>The same QA defect appears repeatedly.<\/li>\n\n\n\n<li>A new content type enters production.<\/li>\n\n\n\n<li>Writers or editors create workarounds outside the template.<\/li>\n\n\n\n<li>A handoff test exposes missing or incorrectly mapped information.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The owner should assess whether a proposed change affects active work, update the field map, and decide whether the change is a revision or a new version. After approval, record the effective date and communicate the change to everyone using the template.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The goal is not to prevent improvement. It is to prevent undocumented drift. A governed template lets the team identify which rules applied to a draft, who owned each decision, and whether the approved source was checked before the CMS release step.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Changing a Google Docs template safely means changing the workflow around it at the same time: audit the fields, assign ownership, version structural changes, protect active assignments, and test the approved document in a CMS draft. Apply the validated replacement to one controlled content handoff first. When you need to move approved Google Docs content into a CMS draft for review, scheduling, or release, evaluate Tenwrite within that process rather than treating automation as a substitute for editorial approval.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn how agency teams can change a Google Docs content template safely. This guide covers field auditing, version decisions, rollout rules, role ownership, and CMS-draft validation before release.<\/p>\n","protected":false},"author":2,"featured_media":1043,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"tenwrite_seo":{"title":"How to Change a Google Docs Template for Agency Workflows","description":"Learn how agencies can change a Google Docs content template safely with field audits, versioning, rollout rules, approval controls, and CMS-draft validation.","focusKeyword":"google docs change template","canonicalUrl":"","noIndex":false,"noFollow":false},"_yoast_wpseo_title":"","_yoast_wpseo_metadesc":"","_yoast_wpseo_focuskw":"","_yoast_wpseo_canonical":"","_yoast_wpseo_meta-robots-noindex":"","_yoast_wpseo_meta-robots-nofollow":"","rank_math_title":"","rank_math_description":"","rank_math_focus_keyword":"","rank_math_canonical_url":"","rank_math_robots":[],"footnotes":""},"categories":[6],"tags":[59,57,60],"class_list":["post-1046","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-google-docs","tag-agency-content-operations","tag-content-approval-workflow","tag-content-operations"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.0.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"Learn how agency teams can change a Google Docs content template safely. This guide covers field auditing, version decisions, rollout rules, role ownership, and CMS-draft validation before release.\" \/>\n\t<meta name=\"robots\" content=\"noindex, nofollow, max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Rupam Poddar\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"Tenwrite Blog - Discover tips and guides on publishing Google Docs to WordPress and Blogger.\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"How to Change a Google Docs Template Without Breaking Your Content Workflow - Tenwrite Blog\" \/>\n\t\t<meta property=\"og:description\" content=\"Learn how agency teams can change a Google Docs content template safely. This guide covers field auditing, version decisions, rollout rules, role ownership, and CMS-draft validation before release.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/08\/7a2fbb94d1.webp\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/08\/7a2fbb94d1.webp\" \/>\n\t\t<meta property=\"og:image:width\" content=\"1600\" \/>\n\t\t<meta property=\"og:image:height\" content=\"900\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-08-11T20:18:18+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-08-11T20:18:18+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:title\" content=\"How to Change a Google Docs Template Without Breaking Your Content Workflow - Tenwrite Blog\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Learn how agency teams can change a Google Docs content template safely. This guide covers field auditing, version decisions, rollout rules, role ownership, and CMS-draft validation before release.\" \/>\n\t\t<meta name=\"twitter:image\" content=\"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/08\/7a2fbb94d1.webp\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"BlogPosting\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\\\/#blogposting\",\"name\":\"How to Change a Google Docs Template Without Breaking Your Content Workflow - Tenwrite Blog\",\"headline\":\"How to Change a Google Docs Template Without Breaking Your Content Workflow\",\"author\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/author\\\/rupam\\\/#author\"},\"publisher\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/#organization\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/wp001.tenwrite.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/7a2fbb94d1.webp\",\"width\":1600,\"height\":900},\"datePublished\":\"2026-08-11T20:18:18+00:00\",\"dateModified\":\"2026-08-11T20:18:18+00:00\",\"inLanguage\":\"en-US\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\\\/#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\\\/#webpage\"},\"articleSection\":\"Google Docs, agency content operations, content approval workflow, content operations\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/wp001.tenwrite.com\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/category\\\/google-docs\\\/#listItem\",\"name\":\"Google Docs\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/category\\\/google-docs\\\/#listItem\",\"position\":2,\"name\":\"Google Docs\",\"item\":\"https:\\\/\\\/wp001.tenwrite.com\\\/category\\\/google-docs\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\\\/#listItem\",\"name\":\"How to Change a Google Docs Template Without Breaking Your Content Workflow\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\\\/#listItem\",\"position\":3,\"name\":\"How to Change a Google Docs Template Without Breaking Your Content Workflow\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/category\\\/google-docs\\\/#listItem\",\"name\":\"Google Docs\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/#organization\",\"name\":\"Tenwrite Blog\",\"description\":\"Discover tips and guides on publishing Google Docs to WordPress and Blogger.\",\"url\":\"https:\\\/\\\/wp001.tenwrite.com\\\/\",\"sameAs\":[\"https:\\\/\\\/www.youtube.com\\\/@tenwrite\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/author\\\/rupam\\\/#author\",\"url\":\"https:\\\/\\\/wp001.tenwrite.com\\\/author\\\/rupam\\\/\",\"name\":\"Rupam Poddar\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\\\/#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/b3549e6840b1384554f94451ec47b32e5227ba632974ff50abee6a185adf885d?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"Rupam Poddar\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\\\/#webpage\",\"url\":\"https:\\\/\\\/wp001.tenwrite.com\\\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\\\/\",\"name\":\"How to Change a Google Docs Template Without Breaking Your Content Workflow - Tenwrite Blog\",\"description\":\"Learn how agency teams can change a Google Docs content template safely. This guide covers field auditing, version decisions, rollout rules, role ownership, and CMS-draft validation before release.\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\\\/#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/author\\\/rupam\\\/#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/author\\\/rupam\\\/#author\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/wp001.tenwrite.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/7a2fbb94d1.webp\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\\\/#mainImage\",\"width\":1600,\"height\":900},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\\\/#mainImage\"},\"datePublished\":\"2026-08-11T20:18:18+00:00\",\"dateModified\":\"2026-08-11T20:18:18+00:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/#website\",\"url\":\"https:\\\/\\\/wp001.tenwrite.com\\\/\",\"name\":\"Tenwrite Blog\",\"description\":\"Discover tips and guides on publishing Google Docs to WordPress and Blogger.\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"How to Change a Google Docs Template Without Breaking Your Content Workflow - Tenwrite Blog","description":"Learn how agency teams can change a Google Docs content template safely. This guide covers field auditing, version decisions, rollout rules, role ownership, and CMS-draft validation before release.","canonical_url":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/","robots":"noindex, nofollow, max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"BlogPosting","@id":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/#blogposting","name":"How to Change a Google Docs Template Without Breaking Your Content Workflow - Tenwrite Blog","headline":"How to Change a Google Docs Template Without Breaking Your Content Workflow","author":{"@id":"https:\/\/wp001.tenwrite.com\/author\/rupam\/#author"},"publisher":{"@id":"https:\/\/wp001.tenwrite.com\/#organization"},"image":{"@type":"ImageObject","url":"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/08\/7a2fbb94d1.webp","width":1600,"height":900},"datePublished":"2026-08-11T20:18:18+00:00","dateModified":"2026-08-11T20:18:18+00:00","inLanguage":"en-US","mainEntityOfPage":{"@id":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/#webpage"},"isPartOf":{"@id":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/#webpage"},"articleSection":"Google Docs, agency content operations, content approval workflow, content operations"},{"@type":"BreadcrumbList","@id":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com#listItem","position":1,"name":"Home","item":"https:\/\/wp001.tenwrite.com","nextItem":{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com\/category\/google-docs\/#listItem","name":"Google Docs"}},{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com\/category\/google-docs\/#listItem","position":2,"name":"Google Docs","item":"https:\/\/wp001.tenwrite.com\/category\/google-docs\/","nextItem":{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/#listItem","name":"How to Change a Google Docs Template Without Breaking Your Content Workflow"},"previousItem":{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/#listItem","position":3,"name":"How to Change a Google Docs Template Without Breaking Your Content Workflow","previousItem":{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com\/category\/google-docs\/#listItem","name":"Google Docs"}}]},{"@type":"Organization","@id":"https:\/\/wp001.tenwrite.com\/#organization","name":"Tenwrite Blog","description":"Discover tips and guides on publishing Google Docs to WordPress and Blogger.","url":"https:\/\/wp001.tenwrite.com\/","sameAs":["https:\/\/www.youtube.com\/@tenwrite"]},{"@type":"Person","@id":"https:\/\/wp001.tenwrite.com\/author\/rupam\/#author","url":"https:\/\/wp001.tenwrite.com\/author\/rupam\/","name":"Rupam Poddar","image":{"@type":"ImageObject","@id":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/b3549e6840b1384554f94451ec47b32e5227ba632974ff50abee6a185adf885d?s=96&d=mm&r=g","width":96,"height":96,"caption":"Rupam Poddar"}},{"@type":"WebPage","@id":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/#webpage","url":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/","name":"How to Change a Google Docs Template Without Breaking Your Content Workflow - Tenwrite Blog","description":"Learn how agency teams can change a Google Docs content template safely. This guide covers field auditing, version decisions, rollout rules, role ownership, and CMS-draft validation before release.","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/wp001.tenwrite.com\/#website"},"breadcrumb":{"@id":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/#breadcrumblist"},"author":{"@id":"https:\/\/wp001.tenwrite.com\/author\/rupam\/#author"},"creator":{"@id":"https:\/\/wp001.tenwrite.com\/author\/rupam\/#author"},"image":{"@type":"ImageObject","url":"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/08\/7a2fbb94d1.webp","@id":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/#mainImage","width":1600,"height":900},"primaryImageOfPage":{"@id":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/#mainImage"},"datePublished":"2026-08-11T20:18:18+00:00","dateModified":"2026-08-11T20:18:18+00:00"},{"@type":"WebSite","@id":"https:\/\/wp001.tenwrite.com\/#website","url":"https:\/\/wp001.tenwrite.com\/","name":"Tenwrite Blog","description":"Discover tips and guides on publishing Google Docs to WordPress and Blogger.","inLanguage":"en-US","publisher":{"@id":"https:\/\/wp001.tenwrite.com\/#organization"}}]},"og:locale":"en_US","og:site_name":"Tenwrite Blog - Discover tips and guides on publishing Google Docs to WordPress and Blogger.","og:type":"article","og:title":"How to Change a Google Docs Template Without Breaking Your Content Workflow - Tenwrite Blog","og:description":"Learn how agency teams can change a Google Docs content template safely. This guide covers field auditing, version decisions, rollout rules, role ownership, and CMS-draft validation before release.","og:url":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/","og:image":"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/08\/7a2fbb94d1.webp","og:image:secure_url":"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/08\/7a2fbb94d1.webp","og:image:width":1600,"og:image:height":900,"article:published_time":"2026-08-11T20:18:18+00:00","article:modified_time":"2026-08-11T20:18:18+00:00","twitter:card":"summary_large_image","twitter:title":"How to Change a Google Docs Template Without Breaking Your Content Workflow - Tenwrite Blog","twitter:description":"Learn how agency teams can change a Google Docs content template safely. This guide covers field auditing, version decisions, rollout rules, role ownership, and CMS-draft validation before release.","twitter:image":"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/08\/7a2fbb94d1.webp"},"aioseo_meta_data":[],"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/wp001.tenwrite.com\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/wp001.tenwrite.com\/category\/google-docs\/\" title=\"Google Docs\">Google Docs<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tHow to Change a Google Docs Template Without Breaking Your Content Workflow\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/wp001.tenwrite.com"},{"label":"Google Docs","link":"https:\/\/wp001.tenwrite.com\/category\/google-docs\/"},{"label":"How to Change a Google Docs Template Without Breaking Your Content Workflow","link":"https:\/\/wp001.tenwrite.com\/how-to-change-a-google-docs-template-without-breaking-your-content-workflow\/"}],"_links":{"self":[{"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/posts\/1046","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/comments?post=1046"}],"version-history":[{"count":0,"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/posts\/1046\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/media\/1043"}],"wp:attachment":[{"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/media?parent=1046"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/categories?post=1046"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/tags?post=1046"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}