Have something to say?

Tell us how we could make the product more useful to you.

Feature Request: Allow Backlink Exchange Automatic Backlinks to Respect a Custom Sitemap, Preferred URL List or an Excluded List

Summary It would be extremely valuable if the Automatic Backlinks feature could be restricted to building links only to pages contained within a user-specified sitemap or preferred URL list. Current Behaviour I've supplied a custom sitemap containing only the strategic pages I want to strengthen, but the Automatic Backlinks feature still appears to discover and build links to older blog posts elsewhere on the site. Why This Is a Problem Many websites contain legacy content that remains online for historical SEO value but is no longer part of the site's current strategy. For example, I have older blog articles that I intentionally keep indexed because they still carry backlinks and search equity. However, I don't want the Automatic Backlinks exchange continuing to strengthen those pages. Instead, I want all new backlinks to reinforce my current authority pages. Suggested Enhancement Please add an option to the Automatic Backlinks feature such as: Only build backlinks to URLs contained in the supplied sitemap Preferred backlink target URLs (user-managed list) Include/Exclude URL patterns (for example /blog/*, /archive/*, /2019/*) This would allow users to decide exactly which pages receive newly generated backlinks. Why This Would Benefit Users Many businesses have: Legacy blog content Archived resources Previous website versions Historical documentation Old articles kept solely for existing SEO equity Those pages should remain indexed by Google, but they are often not the pages site owners want to continue strengthening through the backlink exchange. Giving users control over backlink targets would allow authority to be concentrated on the pages that reflect their current products, services and brand positioning, while preserving the historical value of older content. I suspect this would be particularly valuable for agencies, established businesses and creators who have evolved their websites over time.

Peter Ashby Smith 1 day ago

3

Calendar Scheduling

Feature request: Enable scheduled posting from Arvow directly into the try.journalist app. Why this matters: Arvow already does a strong job aggregating journalist opportunities and surfacing relevant requests. The friction comes after discovery. Today, users still have to manually jump into try.journalist to post responses in real time. That breaks workflow and makes it harder to operate consistently - especially for teams managing multiple brands, clients, or time zones. Adding scheduling would allow users to: Draft responses inside Arvow Schedule posts to go live in try.journalist at optimal times Maintain a predictable cadence rather than reactive, manual posting Coordinate approvals and edits before publication Who benefits: PR teams managing multiple campaigns Founders and operators responding to media while running companies Agencies that need workflow, auditability, and timing control This would meaningfully move Arvow from a discovery tool to a true execution platform—and would be a differentiator versus tools that stop at monitoring.

Todd Daviau 5 months ago

1