RAG retrieval is missing metadata.url and metadata.tags, which blocks compliant Logrock internal links and prevents publishing a finished post.
If you need publish-ready Logrock internal links, the retrieval output has to include the exact URL and tags for every chunk used in linking. Right now, the RAG step is returning generic text without metadata.url (and without tags), so there’s no way to create a compliant internal link map or place valid links in the article.
Once the missing metadata is restored (or you provide a clean list of URLs), the full post can be generated immediately with the required internal linking rules.
What’s broken (and why it matters)
The workflow requires that every internal link come from vector-store retrieval that returns content + metadata.url + metadata.tags for each chunk. When queries to _RAG_Blog_Posts return text without metadata.url or tags, internal links can’t be verified, deduplicated (each URL used once), or placed compliantly.
In practice, this breaks three downstream requirements:
- Internal Link Map: You can’t map links to real Logrock pages without the actual metadata.url.
- Link placement compliance: You can’t guarantee each internal URL is used only once if URLs aren’t returned.
- Auditability: Without tags, links can’t be justified as context-matched to the section topic.
What I need from you to proceed (pick one)
To produce the final article with 4–8 internal links and a working Internal Link Map, you only need to provide one of the two inputs below. Either option is sufficient to move forward and publish.
Option (1): Fix/restore RAG output
Fixing RAG means _RAG_Blog_Posts queries must return chunks that include content, metadata.url, and metadata.tags. Once that output is available, the required internal links can be placed directly from retrieved URLs with proper tag alignment.
- Required fields: content, metadata.url, metadata.tags
- Result: compliant Internal Link Map + valid on-page links
Option (2): Paste 8–12 existing Logrock URLs
Providing 8–12 Logrock URLs (or a sitemap export) allows internal links to be selected and placed immediately, even if RAG metadata is unavailable. The URL list is most useful when it covers key topics that support the target article.
Ideal coverage areas:
- Motor Truck Cargo (MTC) insurance basics
- Commercial truck insurance overview
- Affordable trucking insurance / cost drivers
- Claims documentation / claim denial reasons
- Cargo theft prevention
- COI requirements / broker insurance requirements
- Hotshot insurance
- FMCSA insurance filings / requirements (if available)
After you choose option (1) or (2), the next deliverables are straightforward: rerun RAG (if applicable), generate the Internal Link Map, write the full ~1,800-word article in the mandated structure, add 4–8 internal links (each URL once), and append the Backlink Strategy Brief.
Conclusion: Unblock the internal links, then publish
This post can’t be finalized until internal links can be sourced from real URLs with traceable metadata. Choose option (1) to restore RAG metadata output, or option (2) to share 8–12 Logrock URLs, and the publish-ready article can be generated immediately.
Key Takeaways:
- The blocker is missing metadata.url and metadata.tags in RAG output, which prevents compliant internal linking.
- Fixing retrieval output (option 1) restores a clean, auditable internal link workflow.
- Sharing 8–12 URLs (option 2) enables immediate drafting with 4–8 internal links used once each.
Reply with option (1) or (2), and include the URLs (or confirm RAG is fixed).
