# Reddit Engagement Plan — 30 Days > Goal: build presence in SEO/WP/blogging communities, earn trust before any tool mention > Approach: genuine value first, contextual tool mentions only when directly relevant > Frequency: 3-5 substantive replies per week, no promotional posts --- ## Target Subreddits | Subreddit | Subscribers | Use for | |-----------|-------------|---------| | r/SEO | 300k+ | Technical GSC questions, CTR analysis, content refresh debates | | r/Wordpress | 200k+ | Plugin questions, content workflow, site management | | r/blogging | 200k+ | Content strategy, traffic recovery, monetization context | | r/juststart | 100k+ | Niche site building, GSC analysis, rewrite cycles | | r/bigseo | 35k+ | Advanced SEO, data questions, GSC API, attribution | --- ## Engagement Rules 1. **Never post promotional content.** No "I built a tool" posts in these subs. 2. **Mention the tool only when directly relevant** — e.g., "I have a tool that does this exact thing" in response to someone describing the exact problem it solves. Once per thread, maximum. 3. **Lead with the answer**, not the product. If the answer is complete without mentioning the tool, don't mention it. 4. **Disclose affiliation** if you do mention it: "Disclosure: I built this." 5. **No upvote-farming keywords** — answers should be long enough to be genuinely useful (150+ words for complex questions). 6. **Reply to posts within 2-3 hours of posting** — fresh threads get more visibility. --- ## Weekly Rhythm **Monday/Tuesday:** scan r/SEO and r/bigseo for new GSC questions, traffic drop reports, CTR analysis requests **Wednesday/Thursday:** scan r/juststart and r/blogging for content strategy, rewrite-decision, or traffic-recovery threads **Friday:** scan r/Wordpress for plugin, WP/GSC integration, or content publishing workflow questions --- ## Sample Helpful Answers ### Answer 1 — r/juststart or r/SEO: "How do I decide which posts to rewrite first?" > Common question pattern: "I have 200 posts, GSC shows traffic drops on lots of them, where do I even start?" --- The mistake most people make is sorting by "biggest drop" in raw clicks. That's misleading because it picks up seasonal variance and just ranks your highest-traffic posts (more clicks = more to lose). A better approach: **Step 1: Filter for significance.** A post that dropped from 100 to 80 clicks in a month might just be noise — a 7-day weather pattern, a holiday weekend, a Google test that reverted. Before you touch anything, you need to know whether the drop is statistically real. Compare the same period month-over-month or week-over-week for a rolling 8-week window and calculate whether the change exceeds what you'd expect from normal variance. **Step 2: Cross-reference impressions.** If impressions stayed flat but clicks dropped, that's a CTR problem — title/meta description. If impressions dropped, that's a ranking problem — content quality or freshness. These have different fixes. Don't mix them. **Step 3: Prioritize by opportunity, not damage.** Posts in position 11-25 with high impressions are striking-distance opportunities. They're already getting seen; a rewrite or title tweak can move them to page 1. Posts in position 40+ probably need more than a rewrite — think about whether the page deserves to exist at all. **Step 4: Rewrite for the query that lost, not the post topic.** Pull the specific queries that lost impressions in GSC. That tells you exactly what users were searching for when they stopped finding you. That's the angle to optimize for. The actual rewrite order for most sites: CTR gaps first (fast wins), striking-distance second, significant drops third, everything else later or never. --- ### Answer 2 — r/SEO or r/bigseo: "Does rewriting old content actually work? Looking for data." > Common question pattern: someone skeptical about content refresh ROI --- It works when you do it for the right reasons on the right pages, but most people aren't systematic about it. The published case studies (from HubSpot, Backlinko, others) are real but often cherry-picked — they show the 20% of rewrites that moved the needle, not the 80% that didn't. Here's a more honest breakdown from what I've observed: **When rewrites reliably work:** - Title/meta optimization on pages with high impressions, low CTR, and position 3-8. The page is already ranking; you're just fixing the CTR. I've seen 30-50% CTR improvement from title tests on these pages. - Freshness updates on "best X in [year]" posts where your published year is outdated. Google explicitly uses freshness as a ranking signal for query types that expect current information. - Thin content expansion where your 600-word post is competing against 2,000-word posts on the same query. If their content covers the topic completely and yours doesn't, more depth helps. **When rewrites rarely work:** - Rewrites targeting queries where your domain can't compete (low DA, high competition, no topical authority). - Aesthetic rewrites — changing sentence structure, tone, formatting — without changing the substance of the answer. - Rewrites on pages that lost traffic due to Google algorithm changes affecting the whole query type, not just your specific page (check if your competitors lost too). The key discipline is measuring specific pages with GSC before and after, not just checking overall organic traffic. Overall traffic has too many confounds. --- ### Answer 3 — r/Wordpress: "Is there a way to push content changes from an external tool back to WordPress automatically?" > Common question pattern: someone asking about WP REST API or content workflow automation --- Yes, the WordPress REST API is your friend here. The `/wp/v2/posts` endpoint supports full CRUD — you can create drafts, update content, change status — all from an external app. A few things to get right before building on it: **Authentication:** Don't use Basic Auth in production. Use Application Passwords (built into WordPress core since 5.6) for API key authentication, or OAuth if you need user-level permissions. NEVER expose your WordPress admin credentials to an external service. **Security for server-to-server calls:** If the external service is your own (not a third party), HMAC-SHA256 request signing is the right approach. Each request from the external service carries a signature over the payload and a timestamp; WordPress verifies the signature and rejects replayed requests. This is more secure than Application Passwords for server-to-server because there's no static credential that can be extracted if the service is compromised. **Content snapshots before overwriting:** Whatever you build, create a content snapshot before every external write. WordPress revisions are good but they don't always capture what changed at the API level. A pre-write snapshot in your external system gives you rollback without depending on WP revisions. **Conflict detection:** If a human editor could be editing the post at the same time as your external push, you need conflict detection. The REST API returns `modified` timestamps on posts — compare the timestamp you saw last to the current one before writing. If they diverge, someone else edited it. This is genuinely solvable but there's more surface area than people expect when they first look at it. --- ## Month-End Review At 30 days, assess: - Which subreddits drove the most engagement (upvotes, replies, DMs)? - Any direct tool mentions that converted to signups? (UTM-tag the link if you ever do share it) - Were there questions you couldn't answer well that suggest feature gaps? Adjust week 5+ based on what resonated.