SEO Architect
Run ID: 69cba2d061b1021a29a8af132026-03-31SEO & Growth
PantheraHive BOS
BOS Dashboard

Design a complete SEO site architecture including URL structure, internal linking strategy, content silos, hub-and-spoke models, and technical SEO specifications. Perfect for new sites or major redesigns.

SEO Site Architecture Design: Comprehensive Strategy

This document outlines a robust SEO site architecture designed to maximize organic visibility, improve user experience, and establish strong topical authority. This strategy is suitable for new website builds or significant redesigns, ensuring a solid foundation for long-term SEO success.


1. URL Structure Design

A clean, logical, and keyword-rich URL structure is fundamental for both search engines and users. Our proposed structure emphasizes hierarchy, readability, and keyword relevance.

General Principles:

  • Logical Hierarchy: URLs should reflect the site's content hierarchy, making it easy to understand the relationship between pages.
  • Keyword Inclusion: Integrate primary keywords where natural and concise.
  • Readability: Keep URLs short, descriptive, and easy for users to understand and remember.
  • Hyphens for Separation: Use hyphens (-) to separate words in URLs.
  • Lowercase: All URLs should be lowercase to avoid duplicate content issues.
  • No Redundant Keywords: Avoid keyword stuffing in URLs.
  • Static & Clean: Avoid dynamic parameters (e.g., ?id=123) where possible; use clean, static URLs.
  • Trailing Slashes: Consistent use of trailing slashes (e.g., all URLs end with / or none do).

Proposed Structure Examples:

  • Homepage: https://www.yourdomain.com/
  • Main Service/Category Pages:

* https://www.yourdomain.com/services/

* https://www.yourdomain.com/solutions/

* https://www.yourdomain.com/products/

Example:* https://www.yourdomain.com/digital-marketing/

  • Sub-Service/Sub-Category Pages:

* https://www.yourdomain.com/services/seo-audits/

* https://www.yourdomain.com/digital-marketing/content-marketing/

  • Specific Product/Service Pages:

* https://www.yourdomain.com/products/premium-widget-x/

* https://www.yourdomain.com/digital-marketing/content-marketing/blog-writing-service/

  • Blog/Resource Section:

* https://www.yourdomain.com/blog/

* https://www.yourdomain.com/blog/seo-best-practices/

* https://www.yourdomain.com/blog/seo-best-practices/local-seo-guide/

  • About Us/Contact Us/Legal Pages:

* https://www.yourdomain.com/about-us/

* https://www.yourdomain.com/contact/

* https://www.yourdomain.com/privacy-policy/

Actionable Steps:

  1. Map Content: Create a comprehensive content inventory and map each piece of content to its logical place within the URL hierarchy.
  2. Redirects (for redesigns): Implement 301 redirects for all old URLs to their new counterparts to preserve link equity.
  3. Canonicalization: Ensure proper canonical tags are implemented to prevent duplicate content issues (e.g., www vs. non-www, http vs. https).

2. Internal Linking Strategy

An effective internal linking strategy is crucial for distributing PageRank, improving crawlability, and guiding users through the site, thereby enhancing topical authority.

Key Principles:

  • Contextual Linking: Embed links within the body content of pages, using natural, descriptive, and keyword-rich anchor text. This helps search engines understand the context and relevance of the linked page.
  • Navigational Links:

* Main Navigation: Clear, concise links to primary service/category pages.

* Footer Navigation: Links to important but less primary pages (e.g., About Us, Contact, Privacy Policy, sitemap).

* Breadcrumbs: Implement breadcrumbs on all sub-pages to reinforce hierarchy and improve user navigation (e.g., Home > Category > Subcategory > Page).

  • Silo-Based Linking: Reinforce content silos by linking extensively within a silo, and from spoke pages back up to their hub page. Avoid linking across unrelated silos directly.
  • Related Content/Product Recommendations: Implement modules that suggest related articles, services, or products, providing relevant internal links.
  • Orphan Pages: Regularly audit for "orphan pages" (pages with no incoming internal links) and integrate them into the site's linking structure.

Anchor Text Best Practices:

  • Descriptive: Clearly indicate what the linked page is about.
  • Keyword-Rich (but natural): Include relevant keywords, but avoid exact-match keyword stuffing. Focus on natural language.
  • Vary Anchor Text: Use a variety of anchor texts pointing to the same page to signal a broader range of relevance.

Actionable Steps:

  1. Develop a Linking Map: For each core hub page, identify 5-10 key spoke pages it should link to, and vice-versa.
  2. Content Audits: Periodically review existing content for opportunities to add relevant internal links.
  3. Prioritize High-Value Pages: Ensure your most important pages (e.g., service pages, pillar content) receive a significant number of internal links from relevant, authoritative pages on your site.

3. Content Silos

Content siloing is a strategic approach to organize website content into distinct, thematically related groups. This helps establish clear topical authority for specific subjects, making it easier for search engines to understand your expertise and rank your pages.

Concept:

Imagine your website as a library. Instead of throwing all books onto random shelves, you organize them into sections (e.g., "History," "Science," "Fiction"). Within "Science," you might have "Physics," "Chemistry," etc. Each section is a silo.

Types of Silos:

  • Physical Siloing (Directory-based): Achieved through URL structure and directory organization.

* Example: /digital-marketing/, /digital-marketing/seo/, /digital-marketing/ppc/

  • Virtual Siloing (Internal Linking-based): Achieved primarily through internal linking, where pages within a topic extensively link to each other, but rarely link to pages outside their silo.

Implementation Strategy:

  1. Identify Core Topics: Determine the main thematic areas your business covers (e.g., "SEO Services," "Content Marketing," "Web Design"). These will be your top-level silos.
  2. Map Sub-Topics: For each core topic, identify related sub-topics and specific content pieces (spokes).
  3. URL Structure Reinforcement: Use the proposed URL structure (e.g., yourdomain.com/silo-topic/sub-topic/content-piece/) to visually and structurally reinforce the silos.
  4. Internal Linking Rules:

* Within Silo: Pages within a silo should link extensively to each other.

* Up to Hub: Spoke pages should link back up to their main silo hub page.

* Avoid Cross-Silo Linking: Generally, avoid linking directly from a page in one silo to a page in an unrelated silo, unless absolutely necessary and contextually relevant (e.g., a blog post referencing a related service briefly).

Benefits:

  • Topical Authority: Clearly signals to search engines your site's expertise on specific subjects.
  • Improved Relevance: All content within a silo is highly relevant to its core topic.
  • Enhanced Keyword Rankings: Helps pages rank for a wider array of related keywords.
  • Better User Experience: Users can easily navigate deep into specific topics.

4. Hub-and-Spoke Models

The Hub-and-Spoke model is an advanced form of content siloing that structures content around a central, comprehensive "hub" page (often called pillar content) and several supporting "spoke" pages.

Components:

  • Hub Page (Pillar Content):

* Purpose: A comprehensive, high-level overview of a broad topic. It aims to rank for a broad, high-volume keyword (e.g., "Content Marketing Guide").

* Content: Long-form, evergreen content that covers all essential aspects of the topic without going into excessive detail on any single point.

* Linking: Links out to all relevant spoke pages.

  • Spoke Pages (Cluster Content):

* Purpose: Detailed deep-dives into specific sub-topics mentioned in the hub page. They aim to rank for more specific, long-tail keywords (e.g., "How to Create an Editorial Calendar," "Content Promotion Strategies").

* Content: Focused, in-depth articles, guides, case studies, or tools.

* Linking: Links back to the central hub page, reinforcing its authority and relevance. May also link to other relevant spoke pages within the same cluster.

Example:

  • Hub Page: https://www.yourdomain.com/digital-marketing/content-marketing-guide/

Target Keyword:* "Content Marketing Guide"

  • Spoke Pages:

* https://www.yourdomain.com/digital-marketing/content-marketing-guide/blog-content-strategy/

Target Keyword:* "Blog Content Strategy"

Links back to:* Content Marketing Guide

* https://www.yourdomain.com/digital-marketing/content-marketing-guide/video-marketing-strategy/

Target Keyword:* "Video Marketing Strategy"

Links back to:* Content Marketing Guide

* https://www.yourdomain.com/digital-marketing/content-marketing-guide/content-promotion-tactics/

Target Keyword:* "Content Promotion Tactics"

Links back to:* Content Marketing Guide

Benefits:

  • Enhanced Topical Authority: Clearly demonstrates deep expertise on a subject.
  • Improved Search Visibility: Hub pages gain authority from spokes, and spokes benefit from the hub's overarching relevance.
  • User Experience: Provides a clear path for users to explore a topic from general overview to specific details.
  • Strong Internal Link Equity: Efficiently distributes link value across related content.

Actionable Steps:

  1. Identify Pillar Topics: Brainstorm broad topics relevant to your business that can support extensive sub-topics.
  2. Content Gap Analysis: Identify existing content that can serve as spoke pages, and identify new content needed to build out comprehensive clusters.
  3. Map Hubs and Spokes: Create a detailed plan outlining which spoke pages will support each hub.
  4. Implement Linking: Ensure all spoke pages link back to their hub, and the hub links out to all its spokes.

5. Technical SEO Specifications

Robust technical SEO ensures your site is crawlable, indexable, and performs optimally for both search engines and users.

a. Crawlability & Indexability:

  • Robots.txt:

* Purpose: Directs search engine crawlers on which parts of the site they can or cannot access.

* Specification: Ensure robots.txt is correctly configured to allow crawling of all important content and disallow crawling of non-essential areas (e.g., /wp-admin/, internal search results, staging environments).

  • XML Sitemaps:

* Purpose: Provides search engines with a list of all important pages on your site.

* Specification: Generate an accurate, up-to-date XML sitemap (or multiple sitemaps for large sites, e.g., sitemap_pages.xml, sitemap_blog.xml). Submit to Google Search Console and Bing Webmaster Tools. Include lastmod date.

  • Canonical Tags (<link rel="canonical">):

* Purpose: Prevents duplicate content issues by specifying the preferred version of a page.

* Specification: Implement canonical tags on all pages, pointing to the self-referencing canonical URL. Essential for pages accessible via multiple URLs (e.g., filtered product pages, print versions).

  • noindex / nofollow Meta Tags:

*

gemini Output

SEO Site Architecture Design: Comprehensive Strategy for [Client/Project Name]

Project Overview:

This document outlines a complete SEO site architecture strategy designed to maximize organic visibility, improve user experience, and establish strong topical authority for your website. This architecture is suitable for new sites or significant redesigns, ensuring a robust foundation for long-term SEO success.


1. Introduction: The Power of SEO Site Architecture

A well-planned SEO site architecture is the backbone of a high-performing website. It dictates how search engines crawl, understand, and rank your content, while simultaneously guiding users through a logical and intuitive journey. This strategy focuses on creating a hierarchical, semantically relevant, and technically sound structure that supports both search engine algorithms and human navigation.


2. Foundational Principles of Architecture Design

The following principles guide every aspect of this SEO architecture design:

  • User-Centricity: The structure must be intuitive and easy for users to navigate, leading to a positive user experience (UX) and engagement signals.
  • Crawlability & Indexability: Search engine bots must be able to easily discover, crawl, and index all important pages on the site.
  • Scalability: The architecture should be flexible enough to accommodate future content growth and new topics without requiring a complete overhaul.
  • Semantic Relevance: Pages should be grouped logically by topic, clearly signaling their relevance to search engines and users.
  • Authority Distribution: Internal linking should strategically distribute link equity (PageRank) from high-authority pages to important target pages.

3. URL Structure Design

A clean, logical, and keyword-rich URL structure is crucial for both SEO and user experience.

  • Hierarchy & Logic: URLs should reflect the site's content hierarchy, making it easy to understand the relationship between pages.

* Principle: domain.com/category/subcategory/page-name/

* Example: yourdomain.com/services/seo-audits/technical-seo-audit/

  • Keyword Inclusion: Incorporate relevant keywords naturally in URLs, avoiding keyword stuffing.

* Recommendation: Use primary keywords for the page within its URL segment.

  • Readability & Conciseness: URLs should be easy to read, remember, and share. Keep them as short as possible while retaining descriptive value.

* Avoid: Long strings of numbers, special characters (other than hyphens), or unnecessary parameters.

  • Hyphens for Separators: Always use hyphens (-) to separate words in URLs, not underscores (_). Hyphens are treated as word separators by Google.
  • Lowercase Only: All URLs should be lowercase to prevent duplicate content issues (e.g., domain.com/Page vs. domain.com/page). Implement server-side redirects if necessary.
  • Trailing Slashes (Consistency): Choose a consistent approach for trailing slashes (e.g., domain.com/page/ vs. domain.com/page) and implement 301 redirects to enforce consistency across the site.
  • Canonicalization: For any pages that might have multiple URLs (e.g., tracking parameters, filtered views), implement canonical tags pointing to the preferred version to prevent duplicate content issues.

* Example: <link rel="canonical" href="https://yourdomain.com/preferred-page-url/" />


4. Content Siloing & Hub-and-Spoke Models

Content siloing and hub-and-spoke models are advanced strategies to group related content, establish topical authority, and efficiently distribute link equity.

4.1. Content Silos

Definition: A content silo is a method of organizing website content into distinct, thematically related groups. This strengthens topical relevance and helps search engines understand the expertise of your site on specific subjects.

Purpose:

  • Topical Authority: Signals to search engines that your site has in-depth coverage on a specific topic.
  • Link Equity Flow: Concentrates internal link equity within a silo, strengthening the ranking potential of pages within that topic.
  • Improved UX: Makes it easier for users to find related information.

Types of Siloing:

  1. Directory-Based (URL Structure Siloing): The most straightforward method, where the URL structure itself defines the silo.

* Example:

* /digital-marketing/ (Parent Silo)

* /digital-marketing/seo/ (Child Silo)

* /digital-marketing/ppc/ (Child Silo)

* /digital-marketing/social-media/ (Child Silo)

  1. Internal Linking-Based (Virtual Siloing): Achieved primarily through internal linking, even if the URL structure isn't strictly hierarchical. This is often used to reinforce existing structures or create stronger connections within a silo without changing URLs.

Implementation Steps:

  1. Identify Core Topics: Group your website's content into 3-7 main overarching topics.
  2. Map Sub-Topics: For each core topic, identify 5-20 related sub-topics and individual content pieces.
  3. Design Hierarchy: Create a logical hierarchy from broad topics down to specific articles.
  4. Enforce Linking Rules:

* Vertical Linking: Link from parent pages to child pages, and from child pages back up to parent pages within the same silo.

Horizontal Linking (Limited): Link between pages within the same silo* when relevant, but avoid linking between different silos unless absolutely necessary (and use nofollow if the link is purely navigational and not relevant for authority transfer).

* Navigation: Ensure primary navigation reflects the silo structure.

4.2. Hub-and-Spoke Model (Pillar Content Strategy)

Definition: A specific type of content siloing where a central, comprehensive "Hub" page (often called a Pillar Page) links out to multiple, more detailed "Spoke" pages. The spoke pages, in turn, link back to the hub page.

Purpose:

  • Authority Consolidation: The hub page becomes the authoritative resource for the broad topic, accumulating link equity from its spokes.
  • Semantic Depth: Clearly demonstrates comprehensive coverage of a topic to search engines.
  • User Journey: Provides a clear path for users to delve deeper into specific aspects of a topic.

Components:

  • Hub Page (Pillar Page):

* Nature: A comprehensive, high-level overview of a broad topic. It should be long-form (2,000+ words), evergreen, and answer common questions about the topic.

* Keywords: Targets a broad, high-volume head term.

* Linking Out: Links to all "spoke" pages (cluster content) related to the topic.

* Example: "The Ultimate Guide to Digital Marketing"

  • Spoke Pages (Cluster Content):

* Nature: Detailed articles, guides, case studies, or blog posts that dive deep into specific sub-topics related to the hub.

* Keywords: Targets long-tail keywords and more specific queries.

Linking In: Each spoke page must* link back to its respective hub page, typically using descriptive anchor text.

* Example: "Advanced SEO Techniques," "PPC Campaign Optimization," "Social Media Marketing for Small Businesses" (all linking back to "The Ultimate Guide to Digital Marketing").

Linking Strategy within Hub-and-Spoke:

  • Hub to Spoke: The hub page links to each spoke page, usually from relevant sections within the hub content.
  • Spoke to Hub: Each spoke page links back to the hub page, often using highly relevant anchor text that includes the hub page's target keyword.
  • Spoke to Spoke (Limited): Spoke pages can link to other spoke pages within the same hub-and-spoke model if there's strong contextual relevance, but the primary focus is linking to and from the hub.

5. Internal Linking Strategy

Internal links are fundamental for SEO, distributing link equity, and enhancing user navigation.

  • Purpose:

* SEO: Helps search engines discover new content, understand the hierarchy and relationship between pages, and distribute PageRank (link equity) across the site.

* User Experience: Provides clear navigation paths, reduces bounce rates, and encourages deeper engagement with content.

  • Key Principles:

* Contextual Links: The most powerful internal links are those placed naturally within the body copy of a page, providing additional context or deeper information.

* Anchor Text Optimization: Use descriptive and keyword-rich anchor text (not generic like "click here"). Vary anchor text to avoid over-optimization penalties.

* Example: Instead of "Read more about SEO," use "Learn about advanced SEO techniques."

* Link Depth & Hierarchy: Ensure important pages are not buried too deep within the site (ideally 3-4 clicks from the homepage). The homepage should link to category/silo pages, which then link to sub-category and individual content pages.

* Breadcrumbs: Implement breadcrumb navigation to show users their current location within the site hierarchy and provide internal links back to parent categories.

* Example: Home > Services > SEO Audits > Technical SEO Audit

* Related Content Sections: Implement "Related Posts," "You Might Also Like," or "Recommended Reading" sections on content pages to encourage further exploration within the same silo.

* Navigational Links:

* Main Navigation: Should clearly reflect the top-level silos and most important pages.

* Footer Navigation: Can include links to utility pages (contact, privacy, sitemap) and secondary category links.

* Sidebar Navigation: Useful for displaying sub-categories or popular posts within a specific silo.

  • Implementation Tactics:

* Content Audits: Regularly review existing content for new internal linking opportunities as new pages are published.

* Link Audits: Use tools (e.g., Screaming Frog, Ahrefs, SEMrush) to identify broken internal links, orphaned pages (pages with no internal links), and pages with too few internal links.


6. Technical SEO Specifications for Architecture

Technical SEO ensures that search engines can efficiently access, crawl, interpret, and index your website's content.

  • Crawlability & Indexability:

* Robots.txt: Configure robots.txt to guide search engine crawlers, blocking irrelevant or low-value pages (e.g., admin areas, internal search results, duplicate content) while allowing access to all important content.

* XML Sitemaps: Generate and submit comprehensive XML sitemaps to Google Search Console (and other webmaster tools). Include all canonical, indexable URLs and update regularly.

* Recommendation: Separate sitemaps for different content types (pages, posts, images, videos) if the site is very large.

* Meta Robots Tags: Use meta name="robots" tags on individual pages to control indexing and following behavior (<meta name="robots" content="noindex, nofollow"> for pages you explicitly don't want indexed).

* Canonical Tags: Implement rel="canonical" tags on all pages to specify the preferred version of content, especially for pages with dynamic URLs, pagination, or filtered views.

* URL Parameter Handling: Configure how Google handles URL parameters in Google Search Console to prevent duplicate content issues.

* Site Speed (Core Web Vitals): Optimize server response time, image sizes, render-blocking resources, and leverage caching to ensure fast loading times across all devices. This directly impacts crawl budget and user experience.

* Mobile-First Indexing: Ensure your site is fully responsive and delivers the same content and functionality to mobile users as it does to desktop users. Viewport meta tag is essential.

  • Structured Data (Schema Markup):

* Implement relevant Schema.org markup to provide context to search engines and enable rich snippets in search results.

* Key Types to Consider:

* Organization or LocalBusiness (for company information)

* Article or BlogPosting (for blog posts and articles)

* Product (for e-commerce pages)

* FAQPage (for FAQ sections)

* BreadcrumbList (to enhance breadcrumb navigation in SERPs)

* VideoObject (for embedded videos)

* Validation: Use Google's Rich Results Test tool to validate implementation.

  • HTTPS (SSL Certificate):

* Ensure the entire site operates under HTTPS. This is a ranking factor and essential for security.

* Implement 301 redirects from all HTTP versions of URLs to their HTTPS counterparts.

  • Error Handling:

* Custom 404 Pages: Create user-friendly custom 404 pages that guide users back to relevant content or the homepage.

* 301 Redirects: Implement 301 (permanent) redirects for any pages that are moved, deleted, or have changed URLs, ensuring link equity is preserved and users are directed correctly. Avoid 302 (temporary) redirects for permanent changes.


7. Implementation & Monitoring

  • Phased Rollout (for redesigns): If implementing on an existing site, consider a phased rollout or staging environment testing to minimize risks.
  • Pre-Launch Checklist:

* Verify robots.txt and meta robots tags.

* Validate XML sitemaps.

* Test all internal links for broken links.

* Check canonical tags.

* Run site speed tests.

* Verify HTTPS implementation.

* Confirm custom 404 pages are working.

  • Post-Launch Monitoring:

* Google Search Console: Monitor crawl errors, index coverage reports, sitemap status, and core web vitals.

* Google Analytics: Track user behavior metrics (bounce rate, time on page, pages per session) to identify any navigational issues.

* Rank Tracking: Monitor keyword rankings for target pages.

* Regular Audits: Conduct periodic SEO audits (e.g., quarterly) to identify and rectify any architectural issues that may arise

gemini Output

This deliverable outlines a comprehensive SEO site architecture design, providing a strategic blueprint for optimal search engine visibility, crawlability, and user experience. This architecture is designed to be scalable, maintainable, and highly effective for both new website launches and significant redesigns.

1. Overall Site Architecture Philosophy

The core philosophy behind this SEO site architecture is to create a logical, intuitive, and robust structure that facilitates both user navigation and search engine crawling. By organizing content into clear thematic silos and establishing a strong internal linking framework, we aim to:

  • Enhance Topical Authority: Clearly signal to search engines the site's expertise across specific subject areas.
  • Improve Crawlability & Indexability: Ensure search engines can efficiently discover, crawl, and index all important pages.
  • Distribute PageRank & Link Equity: Strategically pass authority throughout the site, boosting the ranking potential of key pages.
  • Optimize User Experience (UX): Provide a clear, predictable navigation path that helps users find information quickly and easily.
  • Future-Proof Scalability: Design a structure that can easily accommodate future content expansion without compromising SEO performance.

2. URL Structure Design

A clean, consistent, and keyword-rich URL structure is fundamental for SEO and user experience.

  • Principle: URLs should be descriptive, concise, and reflective of the site's hierarchy.
  • Format: https://www.yourdomain.com/category/subcategory/keyword-rich-page-title/

Key Specifications:

  • Readability: Use hyphens (-) to separate words for readability (e.g., keyword-research-guide). Avoid underscores (_) or other special characters.
  • Lowercase Only: All URLs should be lowercase to prevent duplicate content issues (e.g., /Page/ vs /page/).
  • Keyword Inclusion: Incorporate primary target keywords naturally within URLs, especially for category and core content pages.
  • Hierarchy Reflection: URLs should ideally mirror the site's content hierarchy, making it easy for users and search engines to understand the page's context.

Example:* https://www.yourdomain.com/seo-services/technical-seo/crawl-budget-optimization/

  • Conciseness: Keep URLs as short as possible while remaining descriptive. Avoid unnecessary words or parameters.
  • Trailing Slashes: Implement a consistent policy for trailing slashes (e.g., always include or always exclude) and use 301 redirects to enforce it, preventing duplicate content.
  • Avoid Dates/Numbers (unless relevant): For evergreen content, avoid including dates or numerical IDs in the URL unless it's a specific requirement (e.g., news archives, product SKUs).
  • Canonicalization: Ensure proper canonical tags are used to designate the preferred version of a URL in cases of parameter variations or duplicate content.

3. Content Silos Strategy

Content silos are crucial for establishing topical authority and organizing related content. This strategy involves grouping thematically similar content into distinct sections, reinforcing relevance for specific keywords and topics.

  • Concept: Create clear, isolated "folders" of content, where pages within a silo heavily link to each other, but linking between silos is minimal and highly strategic.

Implementation Details:

  • Directory-Based Silos: The primary method will be using URL directories to define silos.

Example Structure:*

* https://www.yourdomain.com/seo-services/ (Silo 1: SEO Services)

* https://www.yourdomain.com/seo-services/technical-seo/

* https://www.yourdomain.com/seo-services/local-seo/

* https://www.yourdomain.com/seo-services/ecommerce-seo/

* https://www.yourdomain.com/content-marketing/ (Silo 2: Content Marketing)

* https://www.yourdomain.com/content-marketing/blog-strategy/

* https://www.yourdomain.com/content-marketing/content-audits/

  • Internal Linking within Silos:

Pages within a silo should extensively link to other relevant pages within that same silo*.

* This strengthens the topical relevance of the entire silo and consolidates link equity around the primary silo topic.

  • Silo Interlinking (Limited):

Linking between* different silos should be done sparingly and only when there is a strong, natural, and highly relevant connection.

* These cross-silo links should typically originate from deeper, more specific pages rather than core hub pages, to avoid diluting topical focus.

  • Content Pillars: Each major silo should ideally have a "pillar page" or "hub page" (see section 4) that acts as the central authority for that topic, linking to all sub-topics within the silo.

4. Internal Linking Strategy & Hub-and-Spoke Models

An effective internal linking strategy is vital for distributing PageRank, improving user navigation, and signaling content relationships to search engines. The Hub-and-Spoke model is a key component of this strategy.

  • Goal: Create a robust network of links that guides both users and search engine crawlers through the site's content efficiently.

Hub-and-Spoke Model (Pillar Content Strategy):

  • Hub Pages (Pillar Content):

* These are comprehensive, authoritative, and often long-form pieces of content that cover a broad topic in depth (e.g., "The Ultimate Guide to SEO").

* Hub pages should link out to all relevant 'Spoke' pages (cluster content) that dive deeper into specific sub-topics.

* They typically reside at a higher level in the site architecture (e.g., domain.com/guide/seo/).

  • Spoke Pages (Cluster Content):

* These are more specific, detailed articles or pages that elaborate on a particular aspect of the broader topic covered by the Hub page (e.g., "Advanced Keyword Research Techniques," "Technical SEO Audit Checklist," "Local SEO Best Practices").

Spoke pages should link back* to their respective Hub page, using relevant anchor text.

* Spoke pages can also link to other highly relevant Spoke pages within the same cluster/silo.

  • Benefits:

* Establishes clear topical authority around the Hub page.

* Consolidates link equity to the Hub, boosting its ranking potential for broad keywords.

* Provides a clear user journey from broad overviews to specific details.

General Internal Linking Guidelines:

  • Contextual Links:

* Embed links naturally within the body copy of content.

* Use descriptive, keyword-rich anchor text that accurately reflects the linked page's content. Avoid generic "click here."

  • Primary Navigation:

* Header and footer navigation should link to the most important top-level pages (e.g., Services, About Us, Contact, main content silos).

* Use clear, concise labels.

  • Breadcrumbs:

* Implement breadcrumbs on all pages (except the homepage) to show the user's current location within the site hierarchy.

Example:* Home > Category > Subcategory > Current Page

* Breadcrumbs are excellent for both UX and SEO, providing a clear path and internal links.

  • Related Content Sections:

* Dynamically display "Related Posts," "Recommended Products," or "Further Reading" sections on relevant pages.

* Ensure these suggestions are genuinely related and not just random.

  • HTML & XML Sitemaps:

* HTML Sitemap: A user-friendly page listing all major sections and pages of the site, aiding navigation for users.

* XML Sitemap: A machine-readable file submitted to search engines (via Google Search Console, Bing Webmaster Tools) listing all pages intended for indexing.

  • Link Depth: Aim to keep all important pages within 3-4 clicks from the homepage to ensure optimal crawlability and PageRank distribution.
  • Audit & Maintenance: Regularly audit internal links for broken links, orphaned pages, and opportunities to strengthen existing connections.

5. Technical SEO Specifications

Robust technical SEO ensures the site is crawlable, indexable, and performs optimally for both users and search engines.

  • Crawlability & Indexability:

* Robots.txt: Configure robots.txt to guide search engine crawlers, blocking access to non-essential or sensitive areas (e.g., admin pages, internal search results, duplicate content filters) while allowing access to all indexable content.

* XML Sitemaps: Generate and regularly update XML sitemaps for all indexable URLs, ensuring they are submitted to Google Search Console and Bing Webmaster Tools.

* Meta Robots Tags: Use noindex for pages not intended for search engine indexing (e.g., thank you pages, internal search results pages with no unique content). Use nofollow on specific links if you do not want to pass link equity (e.g., user-generated content, sponsored links where appropriate).

* Canonical Tags: Implement rel="canonical" tags on all pages to specify the preferred URL, preventing duplicate content issues arising from URL parameters, www vs. non-www, or different versions of content.

  • Site Speed & Core Web Vitals:

* Image Optimization: Compress images, implement lazy loading, and use modern formats (e.g., WebP). Specify image dimensions.

* Minification: Minify CSS, JavaScript, and HTML files to reduce file sizes.

* Browser Caching: Leverage browser caching to store frequently accessed resources locally.

* CDN (Content Delivery Network): Implement a CDN for faster content delivery to users globally.

* Server Response Time: Optimize server performance for quick response times.

* Critical CSS: Inline critical CSS for above-the-fold content to improve Largest Contentful Paint (LCP).

  • Mobile-Friendliness:

* Responsive Design: Implement a fully responsive design that adapts seamlessly to all screen sizes (desktop, tablet, mobile).

* Viewport Meta Tag: Include <meta name="viewport" content="width=device-width, initial-scale=1"> in the <head> of all pages.

* Touch-Friendly Elements: Ensure buttons and links are adequately spaced and sized for touch interaction.

  • Security (HTTPS):

* SSL Certificate: Implement an SSL certificate (HTTPS) across the entire site.

* 301 Redirects: Ensure all HTTP versions of URLs 301 redirect to their HTTPS counterparts.

  • Structured Data (Schema Markup):

* Implement relevant Schema.org markup (JSON-LD recommended) to provide rich snippets in search results. Common types include:

* Article for blog posts and news.

* Product for e-commerce sites.

* LocalBusiness for local businesses.

* FAQPage for frequently asked questions.

* HowTo for instructional content.

* BreadcrumbList for navigation.

* Regularly test structured data using Google's Rich Results Test tool.

  • Error Handling:

* Custom 404 Pages: Design user-friendly 404 pages that guide users back to relevant content or the homepage.

* 301 Redirects: Implement 301 redirects for any moved or deleted pages to preserve link equity and prevent broken links.

* Broken Link Monitoring: Regularly monitor for and fix broken internal and external links.

  • International SEO (if applicable):

* Hreflang Tags: Use hreflang attributes to specify language and regional targeting for multilingual or multiregional websites.

* Geo-Targeting:

seo_architect.md
Download as Markdown
Copy all content
Full output as text
Download ZIP
IDE-ready project ZIP
Copy share link
Permanent URL for this run
Get Embed Code
Embed this result on any website
Print / Save PDF
Use browser print dialog
\n\n\n"); var hasSrcMain=Object.keys(extracted).some(function(k){return k.indexOf("src/main")>=0;}); if(!hasSrcMain) zip.file(folder+"src/main."+ext,"import React from 'react'\nimport ReactDOM from 'react-dom/client'\nimport App from './App'\nimport './index.css'\n\nReactDOM.createRoot(document.getElementById('root')!).render(\n \n \n \n)\n"); var hasSrcApp=Object.keys(extracted).some(function(k){return k==="src/App."+ext||k==="App."+ext;}); if(!hasSrcApp) zip.file(folder+"src/App."+ext,"import React from 'react'\nimport './App.css'\n\nfunction App(){\n return(\n
\n
\n

"+slugTitle(pn)+"

\n

Built with PantheraHive BOS

\n
\n
\n )\n}\nexport default App\n"); zip.file(folder+"src/index.css","*{margin:0;padding:0;box-sizing:border-box}\nbody{font-family:system-ui,-apple-system,sans-serif;background:#f0f2f5;color:#1a1a2e}\n.app{min-height:100vh;display:flex;flex-direction:column}\n.app-header{flex:1;display:flex;flex-direction:column;align-items:center;justify-content:center;gap:12px;padding:40px}\nh1{font-size:2.5rem;font-weight:700}\n"); zip.file(folder+"src/App.css",""); zip.file(folder+"src/components/.gitkeep",""); zip.file(folder+"src/pages/.gitkeep",""); zip.file(folder+"src/hooks/.gitkeep",""); Object.keys(extracted).forEach(function(p){ var fp=p.startsWith("src/")?p:"src/"+p; zip.file(folder+fp,extracted[p]); }); zip.file(folder+"README.md","# "+slugTitle(pn)+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\nnpm install\nnpm run dev\n\`\`\`\n\n## Build\n\`\`\`bash\nnpm run build\n\`\`\`\n\n## Open in IDE\nOpen the project folder in VS Code or WebStorm.\n"); zip.file(folder+".gitignore","node_modules/\ndist/\n.env\n.DS_Store\n*.local\n"); } /* --- Vue (Vite + Composition API + TypeScript) --- */ function buildVue(zip,folder,app,code,panelTxt){ var pn=pkgName(app); var C=cc(pn); var extracted=extractCode(panelTxt); zip.file(folder+"package.json",'{\n "name": "'+pn+'",\n "version": "0.0.0",\n "type": "module",\n "scripts": {\n "dev": "vite",\n "build": "vue-tsc -b && vite build",\n "preview": "vite preview"\n },\n "dependencies": {\n "vue": "^3.5.13",\n "vue-router": "^4.4.5",\n "pinia": "^2.3.0",\n "axios": "^1.7.9"\n },\n "devDependencies": {\n "@vitejs/plugin-vue": "^5.2.1",\n "typescript": "~5.7.3",\n "vite": "^6.0.5",\n "vue-tsc": "^2.2.0"\n }\n}\n'); zip.file(folder+"vite.config.ts","import { defineConfig } from 'vite'\nimport vue from '@vitejs/plugin-vue'\nimport { resolve } from 'path'\n\nexport default defineConfig({\n plugins: [vue()],\n resolve: { alias: { '@': resolve(__dirname,'src') } }\n})\n"); zip.file(folder+"tsconfig.json",'{"files":[],"references":[{"path":"./tsconfig.app.json"},{"path":"./tsconfig.node.json"}]}\n'); zip.file(folder+"tsconfig.app.json",'{\n "compilerOptions":{\n "target":"ES2020","useDefineForClassFields":true,"module":"ESNext","lib":["ES2020","DOM","DOM.Iterable"],\n "skipLibCheck":true,"moduleResolution":"bundler","allowImportingTsExtensions":true,\n "isolatedModules":true,"moduleDetection":"force","noEmit":true,"jsxImportSource":"vue",\n "strict":true,"paths":{"@/*":["./src/*"]}\n },\n "include":["src/**/*.ts","src/**/*.d.ts","src/**/*.tsx","src/**/*.vue"]\n}\n'); zip.file(folder+"env.d.ts","/// \n"); zip.file(folder+"index.html","\n\n\n \n \n "+slugTitle(pn)+"\n\n\n
\n \n\n\n"); var hasMain=Object.keys(extracted).some(function(k){return k==="src/main.ts"||k==="main.ts";}); if(!hasMain) zip.file(folder+"src/main.ts","import { createApp } from 'vue'\nimport { createPinia } from 'pinia'\nimport App from './App.vue'\nimport './assets/main.css'\n\nconst app = createApp(App)\napp.use(createPinia())\napp.mount('#app')\n"); var hasApp=Object.keys(extracted).some(function(k){return k.indexOf("App.vue")>=0;}); if(!hasApp) zip.file(folder+"src/App.vue","\n\n\n\n\n"); zip.file(folder+"src/assets/main.css","*{margin:0;padding:0;box-sizing:border-box}body{font-family:system-ui,sans-serif;background:#fff;color:#213547}\n"); zip.file(folder+"src/components/.gitkeep",""); zip.file(folder+"src/views/.gitkeep",""); zip.file(folder+"src/stores/.gitkeep",""); Object.keys(extracted).forEach(function(p){ var fp=p.startsWith("src/")?p:"src/"+p; zip.file(folder+fp,extracted[p]); }); zip.file(folder+"README.md","# "+slugTitle(pn)+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\nnpm install\nnpm run dev\n\`\`\`\n\n## Build\n\`\`\`bash\nnpm run build\n\`\`\`\n\nOpen in VS Code or WebStorm.\n"); zip.file(folder+".gitignore","node_modules/\ndist/\n.env\n.DS_Store\n*.local\n"); } /* --- Angular (v19 standalone) --- */ function buildAngular(zip,folder,app,code,panelTxt){ var pn=pkgName(app); var C=cc(pn); var sel=pn.replace(/_/g,"-"); var extracted=extractCode(panelTxt); zip.file(folder+"package.json",'{\n "name": "'+pn+'",\n "version": "0.0.0",\n "scripts": {\n "ng": "ng",\n "start": "ng serve",\n "build": "ng build",\n "test": "ng test"\n },\n "dependencies": {\n "@angular/animations": "^19.0.0",\n "@angular/common": "^19.0.0",\n "@angular/compiler": "^19.0.0",\n "@angular/core": "^19.0.0",\n "@angular/forms": "^19.0.0",\n "@angular/platform-browser": "^19.0.0",\n "@angular/platform-browser-dynamic": "^19.0.0",\n "@angular/router": "^19.0.0",\n "rxjs": "~7.8.0",\n "tslib": "^2.3.0",\n "zone.js": "~0.15.0"\n },\n "devDependencies": {\n "@angular-devkit/build-angular": "^19.0.0",\n "@angular/cli": "^19.0.0",\n "@angular/compiler-cli": "^19.0.0",\n "typescript": "~5.6.0"\n }\n}\n'); zip.file(folder+"angular.json",'{\n "$schema": "./node_modules/@angular/cli/lib/config/schema.json",\n "version": 1,\n "newProjectRoot": "projects",\n "projects": {\n "'+pn+'": {\n "projectType": "application",\n "root": "",\n "sourceRoot": "src",\n "prefix": "app",\n "architect": {\n "build": {\n "builder": "@angular-devkit/build-angular:application",\n "options": {\n "outputPath": "dist/'+pn+'",\n "index": "src/index.html",\n "browser": "src/main.ts",\n "tsConfig": "tsconfig.app.json",\n "styles": ["src/styles.css"],\n "scripts": []\n }\n },\n "serve": {"builder":"@angular-devkit/build-angular:dev-server","configurations":{"production":{"buildTarget":"'+pn+':build:production"},"development":{"buildTarget":"'+pn+':build:development"}},"defaultConfiguration":"development"}\n }\n }\n }\n}\n'); zip.file(folder+"tsconfig.json",'{\n "compileOnSave": false,\n "compilerOptions": {"baseUrl":"./","outDir":"./dist/out-tsc","forceConsistentCasingInFileNames":true,"strict":true,"noImplicitOverride":true,"noPropertyAccessFromIndexSignature":true,"noImplicitReturns":true,"noFallthroughCasesInSwitch":true,"paths":{"@/*":["src/*"]},"skipLibCheck":true,"esModuleInterop":true,"sourceMap":true,"declaration":false,"experimentalDecorators":true,"moduleResolution":"bundler","importHelpers":true,"target":"ES2022","module":"ES2022","useDefineForClassFields":false,"lib":["ES2022","dom"]},\n "references":[{"path":"./tsconfig.app.json"}]\n}\n'); zip.file(folder+"tsconfig.app.json",'{\n "extends":"./tsconfig.json",\n "compilerOptions":{"outDir":"./dist/out-tsc","types":[]},\n "files":["src/main.ts"],\n "include":["src/**/*.d.ts"]\n}\n'); zip.file(folder+"src/index.html","\n\n\n \n "+slugTitle(pn)+"\n \n \n \n\n\n \n\n\n"); zip.file(folder+"src/main.ts","import { bootstrapApplication } from '@angular/platform-browser';\nimport { appConfig } from './app/app.config';\nimport { AppComponent } from './app/app.component';\n\nbootstrapApplication(AppComponent, appConfig)\n .catch(err => console.error(err));\n"); zip.file(folder+"src/styles.css","* { margin: 0; padding: 0; box-sizing: border-box; }\nbody { font-family: system-ui, -apple-system, sans-serif; background: #f9fafb; color: #111827; }\n"); var hasComp=Object.keys(extracted).some(function(k){return k.indexOf("app.component")>=0;}); if(!hasComp){ zip.file(folder+"src/app/app.component.ts","import { Component } from '@angular/core';\nimport { RouterOutlet } from '@angular/router';\n\n@Component({\n selector: 'app-root',\n standalone: true,\n imports: [RouterOutlet],\n templateUrl: './app.component.html',\n styleUrl: './app.component.css'\n})\nexport class AppComponent {\n title = '"+pn+"';\n}\n"); zip.file(folder+"src/app/app.component.html","
\n
\n

"+slugTitle(pn)+"

\n

Built with PantheraHive BOS

\n
\n \n
\n"); zip.file(folder+"src/app/app.component.css",".app-header{display:flex;flex-direction:column;align-items:center;justify-content:center;min-height:60vh;gap:16px}h1{font-size:2.5rem;font-weight:700;color:#6366f1}\n"); } zip.file(folder+"src/app/app.config.ts","import { ApplicationConfig, provideZoneChangeDetection } from '@angular/core';\nimport { provideRouter } from '@angular/router';\nimport { routes } from './app.routes';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideZoneChangeDetection({ eventCoalescing: true }),\n provideRouter(routes)\n ]\n};\n"); zip.file(folder+"src/app/app.routes.ts","import { Routes } from '@angular/router';\n\nexport const routes: Routes = [];\n"); Object.keys(extracted).forEach(function(p){ var fp=p.startsWith("src/")?p:"src/"+p; zip.file(folder+fp,extracted[p]); }); zip.file(folder+"README.md","# "+slugTitle(pn)+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\nnpm install\nng serve\n# or: npm start\n\`\`\`\n\n## Build\n\`\`\`bash\nng build\n\`\`\`\n\nOpen in VS Code with Angular Language Service extension.\n"); zip.file(folder+".gitignore","node_modules/\ndist/\n.env\n.DS_Store\n*.local\n.angular/\n"); } /* --- Python --- */ function buildPython(zip,folder,app,code){ var title=slugTitle(app); var pn=pkgName(app); var src=code.replace(/^\`\`\`[\w]*\n?/m,"").replace(/\n?\`\`\`$/m,"").trim(); var reqMap={"numpy":"numpy","pandas":"pandas","sklearn":"scikit-learn","tensorflow":"tensorflow","torch":"torch","flask":"flask","fastapi":"fastapi","uvicorn":"uvicorn","requests":"requests","sqlalchemy":"sqlalchemy","pydantic":"pydantic","dotenv":"python-dotenv","PIL":"Pillow","cv2":"opencv-python","matplotlib":"matplotlib","seaborn":"seaborn","scipy":"scipy"}; var reqs=[]; Object.keys(reqMap).forEach(function(k){if(src.indexOf("import "+k)>=0||src.indexOf("from "+k)>=0)reqs.push(reqMap[k]);}); var reqsTxt=reqs.length?reqs.join("\n"):"# add dependencies here\n"; zip.file(folder+"main.py",src||"# "+title+"\n# Generated by PantheraHive BOS\n\nprint(title+\" loaded\")\n"); zip.file(folder+"requirements.txt",reqsTxt); zip.file(folder+".env.example","# Environment variables\n"); zip.file(folder+"README.md","# "+title+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\npython3 -m venv .venv\nsource .venv/bin/activate\npip install -r requirements.txt\n\`\`\`\n\n## Run\n\`\`\`bash\npython main.py\n\`\`\`\n"); zip.file(folder+".gitignore",".venv/\n__pycache__/\n*.pyc\n.env\n.DS_Store\n"); } /* --- Node.js --- */ function buildNode(zip,folder,app,code){ var title=slugTitle(app); var pn=pkgName(app); var src=code.replace(/^\`\`\`[\w]*\n?/m,"").replace(/\n?\`\`\`$/m,"").trim(); var depMap={"mongoose":"^8.0.0","dotenv":"^16.4.5","axios":"^1.7.9","cors":"^2.8.5","bcryptjs":"^2.4.3","jsonwebtoken":"^9.0.2","socket.io":"^4.7.4","uuid":"^9.0.1","zod":"^3.22.4","express":"^4.18.2"}; var deps={}; Object.keys(depMap).forEach(function(k){if(src.indexOf(k)>=0)deps[k]=depMap[k];}); if(!deps["express"])deps["express"]="^4.18.2"; var pkgJson=JSON.stringify({"name":pn,"version":"1.0.0","main":"src/index.js","scripts":{"start":"node src/index.js","dev":"nodemon src/index.js"},"dependencies":deps,"devDependencies":{"nodemon":"^3.0.3"}},null,2)+"\n"; zip.file(folder+"package.json",pkgJson); var fallback="const express=require(\"express\");\nconst app=express();\napp.use(express.json());\n\napp.get(\"/\",(req,res)=>{\n res.json({message:\""+title+" API\"});\n});\n\nconst PORT=process.env.PORT||3000;\napp.listen(PORT,()=>console.log(\"Server on port \"+PORT));\n"; zip.file(folder+"src/index.js",src||fallback); zip.file(folder+".env.example","PORT=3000\n"); zip.file(folder+".gitignore","node_modules/\n.env\n.DS_Store\n"); zip.file(folder+"README.md","# "+title+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\nnpm install\n\`\`\`\n\n## Run\n\`\`\`bash\nnpm run dev\n\`\`\`\n"); } /* --- Vanilla HTML --- */ function buildVanillaHtml(zip,folder,app,code){ var title=slugTitle(app); var isFullDoc=code.trim().toLowerCase().indexOf("=0||code.trim().toLowerCase().indexOf("=0; var indexHtml=isFullDoc?code:"\n\n\n\n\n"+title+"\n\n\n\n"+code+"\n\n\n\n"; zip.file(folder+"index.html",indexHtml); zip.file(folder+"style.css","/* "+title+" — styles */\n*{margin:0;padding:0;box-sizing:border-box}\nbody{font-family:system-ui,-apple-system,sans-serif;background:#fff;color:#1a1a2e}\n"); zip.file(folder+"script.js","/* "+title+" — scripts */\n"); zip.file(folder+"assets/.gitkeep",""); zip.file(folder+"README.md","# "+title+"\n\nGenerated by PantheraHive BOS.\n\n## Open\nDouble-click \`index.html\` in your browser.\n\nOr serve locally:\n\`\`\`bash\nnpx serve .\n# or\npython3 -m http.server 3000\n\`\`\`\n"); zip.file(folder+".gitignore",".DS_Store\nnode_modules/\n.env\n"); } /* ===== MAIN ===== */ var sc=document.createElement("script"); sc.src="https://cdnjs.cloudflare.com/ajax/libs/jszip/3.10.1/jszip.min.js"; sc.onerror=function(){ if(lbl)lbl.textContent="Download ZIP"; alert("JSZip load failed — check connection."); }; sc.onload=function(){ var zip=new JSZip(); var base=(_phFname||"output").replace(/\.[^.]+$/,""); var app=base.toLowerCase().replace(/[^a-z0-9]+/g,"_").replace(/^_+|_+$/g,"")||"my_app"; var folder=app+"/"; var vc=document.getElementById("panel-content"); var panelTxt=vc?(vc.innerText||vc.textContent||""):""; var lang=detectLang(_phCode,panelTxt); if(_phIsHtml){ buildVanillaHtml(zip,folder,app,_phCode); } else if(lang==="flutter"){ buildFlutter(zip,folder,app,_phCode,panelTxt); } else if(lang==="react-native"){ buildReactNative(zip,folder,app,_phCode,panelTxt); } else if(lang==="swift"){ buildSwift(zip,folder,app,_phCode,panelTxt); } else if(lang==="kotlin"){ buildKotlin(zip,folder,app,_phCode,panelTxt); } else if(lang==="react"){ buildReact(zip,folder,app,_phCode,panelTxt); } else if(lang==="vue"){ buildVue(zip,folder,app,_phCode,panelTxt); } else if(lang==="angular"){ buildAngular(zip,folder,app,_phCode,panelTxt); } else if(lang==="python"){ buildPython(zip,folder,app,_phCode); } else if(lang==="node"){ buildNode(zip,folder,app,_phCode); } else { /* Document/content workflow */ var title=app.replace(/_/g," "); var md=_phAll||_phCode||panelTxt||"No content"; zip.file(folder+app+".md",md); var h=""+title+""; h+="

"+title+"

"; var hc=md.replace(/&/g,"&").replace(//g,">"); hc=hc.replace(/^### (.+)$/gm,"

$1

"); hc=hc.replace(/^## (.+)$/gm,"

$1

"); hc=hc.replace(/^# (.+)$/gm,"

$1

"); hc=hc.replace(/\*\*(.+?)\*\*/g,"$1"); hc=hc.replace(/\n{2,}/g,"

"); h+="

"+hc+"

Generated by PantheraHive BOS
"; zip.file(folder+app+".html",h); zip.file(folder+"README.md","# "+title+"\n\nGenerated by PantheraHive BOS.\n\nFiles:\n- "+app+".md (Markdown)\n- "+app+".html (styled HTML)\n"); } zip.generateAsync({type:"blob"}).then(function(blob){ var a=document.createElement("a"); a.href=URL.createObjectURL(blob); a.download=app+".zip"; a.click(); URL.revokeObjectURL(a.href); if(lbl)lbl.textContent="Download ZIP"; }); }; document.head.appendChild(sc); } function phShare(){navigator.clipboard.writeText(window.location.href).then(function(){var el=document.getElementById("ph-share-lbl");if(el){el.textContent="Link copied!";setTimeout(function(){el.textContent="Copy share link";},2500);}});}function phEmbed(){var runId=window.location.pathname.split("/").pop().replace(".html","");var embedUrl="https://pantherahive.com/embed/"+runId;var code='';navigator.clipboard.writeText(code).then(function(){var el=document.getElementById("ph-embed-lbl");if(el){el.textContent="Embed code copied!";setTimeout(function(){el.textContent="Get Embed Code";},2500);}});}