A workflow that improves existing website pages for SEO by finding missing search terms and phrases, then adding an FAQ section with links to related pages. The FAQ can use Schema.org’s FAQPage format, which helps search engines understand the questions and answers.
A tool for generating H1 headings, page titles, and meta descriptions for Yandex search. It can work deeply from search-result research or in bulk from an existing playbook and page data.
An end-to-end SEO strategy workflow that scans a client website, reviews metrics and competitors, finds growth opportunities, and produces strategy documents and estimates.
A website-structure planning workflow based on an existing SEO analysis. It builds a page list from competitor research, target searches, search results, and checks for keyword cannibalisation—when pages compete for the same search query.
A complete technical SEO audit workflow for Yandex, the Russian search engine. It examines indexing, technical health, URLs, metadata, structured data, JavaScript, analytics, user behaviour, and links.
A blog-topic planning task that creates 15–25 topics in a worktree, saves them in an XLSX spreadsheet, and uploads the result to Google Drive as a Google Sheet.
A file-sharing task that uploads an article saved as a DOCX document to Google Drive and converts it into a Google Doc. It also records the delivery link in metadata.
A file-sharing task that uploads a DOCX FAQ document to Google Drive and converts it into a Google Doc. The file contains both written answers and Schema.org data for search engines.
A file-sharing task that uploads an SEO strategy document and a budget spreadsheet to Google Drive, converting them into a Google Doc and Google Sheet.
A project-update tool that synchronizes selected machinery files from a local seo-pipeline-template into a project while leaving client files and working folders untouched.
An intake step that reads project material such as briefs, call transcripts, prices, old websites, photos, and scans, or starts with an empty input folder. It extracts business details, legal information, facts, constraints, and unanswered questions into parts/facts.json.
A market-research step that turns project input into a summary of target audiences, competitors, customer language, and the proposed offer. It stores the result in parts/market.json.
A pre-project discovery workflow for learning about a client's business before writing website content. It asks three questions, researches competing sites, and produces a project contract plus two client documents.
An SEO research agent for a defined analysis project. SEO means improving a website's visibility in search results; this agent gathers competing domains and search-result findings into project files.
A Russian-language website copywriting workflow based on a defined process, including competitor analysis, page types, content strategy, pilots, audits, and a one-file prototype.
A sales-outcome tracking command that records what happened after a strategy was sent, including replies, calls, wins or losses, the selected estimate, and rejection reasons. The data is stored in JSON files.
★not rated 2
changed 4d agoB125 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: