Editorial Policy

Screpy publishes SEO, monitoring, reporting, and product-led content to help readers make clearer decisions. Our goal is practical guidance, not generic keyword coverage.

This policy explains how the Screpy Editorial Team writes, reviews, updates, and corrects content across blog posts, SEO tasks, feature pages, and other educational pages.

We write for marketers, founders, agencies, and technical teams who need useful SEO decisions. Pages should answer a real question, support a real workflow, or explain a feature with enough context to help a reader act.

Non-obvious claims should be supported by primary sources, official documentation, product evidence, public data, or direct Screpy experience.

• People-first SEO guidance instead of thin search coverage.
• Product and technical accuracy for Screpy workflows.
• Clear sourcing for claims that readers should be able to verify.
• Useful updates when search behavior, platform features, or product capabilities change.

Topics are selected by search intent, customer value, and their connection to technical SEO, website monitoring, content quality, or reporting workflows.

Drafts are reviewed for clarity, factual accuracy, source quality, product relevance, and whether the page gives the reader a useful next step.

• Topic selection based on reader need and business relevance.
• Drafting around the decision or task the reader needs to complete.
• Editorial review by the Screpy Editorial Team.
• Maintenance through updates, merges, redirects, or removals when content no longer earns its place.

Where freshness and trust matter, Screpy pages should show author, reviewer, published date, and last reviewed date signals.

Recommendations should stay aligned with Google Search documentation, major search platform changes, and practical SEO tooling behavior.

• Use specific examples, constraints, screenshots, product context, or source links when they make guidance easier to verify.
• Avoid inflated claims, undisclosed sponsorships, unsupported statistics, and generic AI-generated filler.
• Keep visible review dates consistent with structured data where structured data is present.

If you notice outdated information, an unclear recommendation, a broken source, or a factual issue, contact us. We review correction requests against the page, product behavior, source material, and current SEO context.

When a meaningful change is needed, we update the page and its reviewed date.