The new product marketing lead is hired to drive scientific content, demand generation and e-commerce conversion. But robots.txt says "Disallow: /blog", and that one line covers all 103 /blog/ URLs in the sitemap, including the guides scientists search for before they pick a kit: how to choose an RNA-seq strategy, why lncRNA coverage matters, RPA vs. LAMP, and how to choose a library amplification mix. Those guides have no /news/ copy, so search engines are told not to read Watchmaker's best top-of-funnel content.
First action
Edit robots.txt today and use Search Console's URL inspection on the RNA-seq guide.
How to measure it
Organic sessions on /blog/post/ guides
- Now
- –
- Target
- 1,500 a month
- By
- 90 days
Steps
Confirm the block
Check the six guides with Search Console URL inspection.
Web and e-commerce lead 1 hour
Edit robots.txt
Remove "Disallow: /blog"; keep author and private paths only.
Web and e-commerce lead 1 hour
Add canonicals
Self-canonicals on guides; news duplicates point to /news/.
Web and e-commerce lead 1 day
Resubmit
Sitemap and the top 20 guides for indexing.
Web and e-commerce lead 1 hour
Add next steps
Each guide links to its kit page and a sample request.
Associate Director, Product Marketing 3 days
Track
Impressions, clicks and sample requests from guides.
Associate Director, Product Marketing weekly
Why it works
Remove the blanket "/blog" rule (keep only the author and test paths you want hidden), add a self-canonical to each post, point the /blog/post/ news duplicates at their /news/ versions, and resubmit the sitemap in Search Console. Then link each guide to the matching kit page and a "request a sample" form, so readers who arrive from search have a next step.
These guides answer the questions labs ask while they are choosing a workflow. Once search engines and AI assistants can read them, they can bring in new labs every month at no media cost.
Ready to use
Checklistrobots.txt fix list
[ ] Remove "Disallow: /blog" [ ] Keep "Disallow: /blog/author/..." lines if wanted [ ] Self-canonical on every /blog/post/ guide [ ] News posts: canonical to /news/<slug> [ ] Check "/contact" and "/catalog/" rules (idea 2) [ ] Resubmit sitemap in Search Console [ ] Inspect the six guides after a week
Risks and how to handle them
Old event posts come back into search
Mark past-event posts noindex or redirect them to the events page.
Duplicate news pages compete
Use canonicals to the /news/ version.
Evidence
- Your websiterobots.txt (checked twice on October 22, 2026) contains "Disallow: /blog", which covers every /blog/post/ address, yet the sitemap lists 103 /blog/ URLs. Watchmaker's educational guides live only there: "How to Choose the Right RNA-Seq Strategy", "Beyond Protein-Coding Genes: Why lncRNA Coverage Matters in RNA Sequencing", "How to get methylation and variant data from a single NGS library", "RPA vs. LAMP: Choosing the Right Isothermal Amplification Method", "Understanding RPA and When to Use It" and "How to Choose a Library Amplification Mix: Five Metrics That Matter". News posts also have /news/ copies, but these guides return "page not found" at /news/.Source
- HiringAssociate Director, Product Marketing (posted August 26, 2026, Boulder or remote, reporting to the VP Marketing): leads a team for "product commercialization, technical marketing, scientific content development, and commercial execution"; will "Own the overall product positioning framework and unified communication strategy", guide "publication strategy", and "Support the advancement of digital marketing initiatives, including demand generation, lead management, and e-commerce, to expand market reach, strengthen customer acquisition and conversion".Source
- Your websiteOther robots.txt rules: "Disallow: /contact" (which also matches /contact-us and /contact-new-account), "Disallow: /catalog/" while the sitemap lists /catalog/product/view/id/ pages, and "Disallow: /asset/download/file/", the path the resource library uses for downloads. Pages carry no canonical tag, and the same news post is served at both /news/ and /blog/post/.Source