shopline-onpage-implement

Audit and implement on-page SEO changes for Shopline stores via API.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/bolun-ben-ship/RightClickAI-seo-workspace --skill shopline-onpage-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shopline-onpage-implement
Source: https://github.com/bolun-ben-ship/RightClickAI-seo-workspace/tree/main/seo-workflow/shopline-onpage-implement
Command: npx skills add https://github.com/bolun-ben-ship/RightClickAI-seo-workspace --skill shopline-onpage-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

On-page SEO for Shopline stores is a multi-step, data-heavy process. This workflow orchestrates historical context loading, comprehensive audits, performance data retrieval, live store snapshot collection via Shopline Admin REST API, last-30-days market research, and a prioritised implementation plan with before/after values. It then presents an approval UI and executes approved on-page changes (SEO titles, meta descriptions, and schema) via the API, saving a post-implementation report. It always builds on prior months, never re-recommending items that were resolved.

Core Features & Use Cases

  • End-to-end on-page SEO orchestration for Shopline stores, including data gathering, analysis, and automated execution.
  • Prioritised implementation planning with before/after value projections and an approval workflow.
  • Post-implementation reporting to track impact and guard against regressions.
  • Fully credential-safe: collects store-specific values at startup and uses Shopline API calls for changes.

Quick Start

Start by providing your Shopline store handle and access token to initialize the on-page SEO workflow for that store.

Frequently Asked Questions about shopline-onpage-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate on-page SEO audits and implementation for my Shopline store?

Automating Shopline on-page SEO involves orchestrating data gathering, performance analysis, and API execution for SEO titles, meta descriptions, and schema. This workflow builds a prioritized implementation plan from audit data and live store snapshots, then executes approved changes automatically via the Shopline Admin REST API.

Can I update Shopline metafields and SEO schema automatically through the API?

Yes, you can update Shopline metafields and SEO schema automatically via API calls. This workflow executes approved on-page changes including SEO titles, meta descriptions, and schema directly through the Shopline Admin REST API, requiring no hard-coded credentials to modify store data.

What is the best way to audit on-page SEO for Shopline without repeating past recommendations?

The best way to audit on-page SEO without repeating past recommendations is loading historical context before analysis. This workflow builds on prior months' reports, carrying forward unresolved items and never re-recommending SEO elements that were previously resolved.

Do I need to hardcode my Shopline API credentials to automate on-page SEO changes?

No, you do not need to hardcode Shopline API credentials to automate on-page SEO changes. This workflow is fully credential-safe, collecting store-specific values like your store handle and access token at startup to authenticate API calls dynamically.

How does on-page SEO automation handle implementation planning and approval?

On-page SEO automation handles implementation planning by gathering live store snapshots and performance data to build a prioritized plan with before and after value projections. It then presents an approval UI, ensuring you review and authorize all proposed SEO changes before execution.

What happens to unresolved SEO items after an automated Shopline implementation cycle?

Unresolved SEO items after an automated Shopline implementation cycle are carried forward to the next iteration. The workflow saves a post-implementation report tracking impact and guarding against regressions, building on historical context so prior unresolved audit items remain visible.