Juniper Square is hiring an SEO & AEO Manager to own crawl efficiency, indexing and authority, measured by referring domains and citations. Today every old blog.junipersquare.com address we tried, including the one linked from every Juniper Square job post, answers with a temporary 302 redirect to the homepage over plain http. The articles still exist at www.junipersquare.com/blog/ with the same slug, so a press mention, partner page or old social post that links to a 2023 venture capital report or a podcast interview drops the reader on the homepage, and search engines are told the move is temporary.
First action
Export the old blog URLs with the most external links and test them.
How to measure it
Old blog URLs resolving to the matching article with a 301
- Now
- –
- Target
- 100% of linked URLs
- By
- 30 days
Steps
List old URLs
From backlink data and the 271-post sitemap.
SEO & AEO Manager 1 day
Write the rule
Path-preserving 301 to https www, root to /blog.
Web engineering agency 1 day
Handle misses
Unmatched paths to the closest topic page.
SEO & AEO Manager 2 days
Fix own links
Job-post boilerplate and old emails.
Talent Acquisition 1 day
Test
Top 100 linked old URLs.
SEO & AEO Manager 1 day
Watch
Search Console and referring domains for eight weeks.
SEO & AEO Manager weekly
Why it works
Replace the blanket rule with one permanent (301) rule that keeps the path: blog.junipersquare.com/<slug> to https://www.junipersquare.com/blog/<slug>, and the blog root to /blog. Send any old address with no match to the closest topic page, not the homepage. Update the job-post boilerplate link, then check the top linked old URLs in Search Console and a backlink tool.
Years of links earned by the blog start counting for the right pages again, readers land on what they clicked, and the new hire starts with a clean technical base for AI citations.
Ready to use
ChecklistOld blog redirect checklist
[ ] blog.junipersquare.com/<slug> -> https://www.junipersquare.com/blog/<slug> (301) [ ] blog.junipersquare.com/ -> https://www.junipersquare.com/blog (301) [ ] No http hop, no chain [ ] Retired posts mapped to the closest article or guide [ ] Job-post boilerplate link updated [ ] Top 100 linked URLs tested [ ] Referring domains tracked for eight weeks
Risks and how to handle them
Some old posts were retired
Map them to the closest current article or guide, never a blanket homepage redirect.
Evidence
- Redirect checkChecked twice on October 23, 2026: blog.junipersquare.com and every old post address we tried (the digital-first workplace article linked from the job posts, a Q3 2023 venture capital report, a podcast interview and a CEO profile) answer with a temporary 302 redirect to the homepage over plain http (http://www.junipersquare.com/). The same articles are live at www.junipersquare.com/blog/ with the same slug.Source
- HiringSEO & AEO Manager (posted September 24, 2026): owns "how we're found, ranked, and cited, in traditional search and in the AI answer engines"; must "Own SEO across junipersquare.com: on-page optimization, site architecture, internal linking, Core Web Vitals", "Monitor and improve sitewide crawl efficiency and indexing", and manage "structured data (JSON-LD) and emerging AI crawling protocols, including llms.txt and plain-text/markdown alternates of priority pages"; extend visibility to "Reddit threads, YouTube" and review sites; build authority so "referring domains and citations from private markets and financial media keep growing".Source
- HiringEvery Juniper Square job post says: "the Operations Partner trusted by 2,300+ GPs", "$300B+ under administration and 700,000+ LPs on platform", JunieAI, "$350M+ in funding", "1,000+ employees", and links to a blog.junipersquare.com article about its digital-first workplace.Source
- Your websiteSitemap (814 URLs, October 23, 2026): 271 blog posts, 151 podcast pages, 58 videos, 56 customer stories, 52 news items, 47 guides; no comparison pages; the latest seasonal "What's new" product update page is from 2025. /llms.txt returns 404, while robots.txt explicitly allows GPTBot, ChatGPT-User, anthropic-ai, Claude-Web and Google-Extended.Source