...
Purpose
This guide outlines the process of resolving content issues across the entire fulfillment process. These issues are solely issues that arise between teams. Issues contained to one team should be resolved through direct communication between the supervisor and reportSEO rep.
Content to SEO
When Content identifies an issue that SEO must resolve, the process is as follows:
The Content Writer describes the issue and what needs to be changed (when known) in a comment on the Trello card.
The Content Writer clicks the “Issues for SEO” button.
Internal Note: The Content Writer fills out the appropriate information in the kickback sheet for leads to analyze at the end of the month. SEO reps are not involved in this step.
The card moves to the “Issues from Content” column on the Dealer Spike SEO Content Staging Board.
The SEO rep reviews the issue described on the card and updates the card accordingly, including any details impacted by the changes made.
Example: If a pagefooter request is kicked back because there is an existing pagefooter on that site fewer than six months old, the rep must update the keyword focus and the link to the ILP for the issue to be completely resolved.
...
Note to Leads: Should writers tag SEO reps in their comment or will they be expected to monitor the issues columns?
The SEO rep clicks the appropriate monthly request button to send it to the corresponding column on the Dealer Spike Content Writing Board, NOT to a writer’s in-progress column.
The process will repeat if, upon review, the Content Writer is not satisfied with the corrections.
QA to SEO
When QA identifies an issue that SEO must resolve, the process is as follows:
The QA Specialist describes the issue and what needs to be changed (when known) in a comment on the Trello card.
The QA Specialist clicks the “Issues for SEO” button.
The card moves to the “Issues from Content” column on the Dealer Spike SEO Content Staging Board.
Internal Note: QA requests very few corrections from SEO during the content process. It is more efficient for QA to share the “Issues from Content” column as opposed to creating a new column that would largely remain empty. SEO reps must note when an issue is raised by a QA specialist or comes from the Dealer Spike Content QA board so they know which process to follow.
The SEO rep reviews the issue described on the card and updates the card accordingly, including any details impacted by the changes made.
...
The SEO rep clicks the “Send to QA” button to send it to the Dealer Spike Content QA Board.
The process will repeat if, upon review, the QA Specialist is not satisfied with the corrections.
Posting to SEO
When the Juniper posting team identifies an issue that SEO must resolve, the process is as follows:
The Juniper rep describes the issue and what needs to be changed (when known) in a comment on the Trello card.
The Juniper rep clicks the “Issues for SEO” button.
The card moves to the “Issues from Posting” column on the Dealer Spike SEO Content Staging Board.
The SEO rep reviews the issue described on the card and resolves the issue accordingly, including any details impacted by the changes made.
...
The SEO rep clicks the “Send to Posting” button to send it to the Dealer Spike Content Posting Board.
The process will repeat if, upon review, the Juniper rep is not satisfied with the corrections.
QA to Content
When QA identifies an issue that Content must resolve, the process is as follows:
The QA Specialist describes the issue and what needs to be changed (when known) in a comment on the Trello card.
The QA Specialist clicks the “Issues for Content” button.
The card moves to the “Issues from QA” column on the Dealer Spike Content Writing Board.
The Content Writer reviews the issue described on the card and resolves the issue accordingly, including any details impacted by the changes made.
The Content Writer clicks their corresponding QA button to send it to the Dealer Spike Content QA Board.
The process will repeat if, upon review, the QA Specialist is not satisfied with the corrections.
Posting to Content
When the Juniper posting team identifies an issue that Content must resolve, the process is as follows:
The Juniper rep describes the issue and what needs to be changed (when known) in a comment on the Trello card.
The Juniper rep clicks the “Issues for Content” button.
The card moves to the “Issues from Posting” column on the Dealer Spike Content Writing Board.
The Content Writer reviews the issue described on the card and resolves the issue accordingly, including any details impacted by the changes made.
The Content Writer clicks the “Send to Posting” button to send it to the Dealer Spike Content Posting Board.
The process will repeat if, upon review, the Juniper rep is not satisfied with the corrections.