Troubleshooting: Other Issues

🔐 Resolve a Website Ownership Conflict

🔎 Why this happens Search Atlas prevents duplicate website listings to protect site data and workspace access. You may see an ownership conflict when the website is already connected to another workspace, was added by a former team member, or is listed under a different version of the domain. ✅ Check the website details 1. Open Website Studio from the left sidebar. 2. Confirm that you entered the correct domain, including the spelling and domain extension. 3. Check whether the website uses a different version, such as www versus the root domain, or a different subdomain. 4. Do not create a second listing for the same website. 🛠️ Verify your ownership Make sure you can access the website or its domain settings. If Search Atlas provides an ownership verification step, complete it using the available instructions. The verification must be added to the exact website version shown in the platform. If you manage the website through a team, confirm that you have permission to edit its files, DNS settings, or connected publishing account. Being the website owner does not always mean your Search Atlas account has access to an existing listing. 👥 Request access from the current owner If another workspace already contains the website, contact the person who originally added it and ask them to review the listing and provide access or remove it if it is no longer needed. This is usually the fastest way to resolve a legitimate shared-ownership situation. If the website belongs to a previous employee, agency, or workspace, gather proof that you control the domain and identify the existing listing details before requesting a transfer or correction. 🚫 Avoid common mistakes - Do not repeatedly submit the same website. - Do not add a temporary subdomain to bypass an ownership conflict. - Do not remove verification records unless you understand which listing they belong to. - Confirm that you are working in the correct Search Atlas workspace. 💬 Get help resolving the conflict If the website is yours but remains unavailable after checking the details and completing verification, include the domain, the Search Atlas workspace you are using, and a screenshot of the conflict message when requesting help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔐 Resolve Website Ownership Conflicts

🔎 Why the conflict appears Search Atlas prevents the same website from being added more than once when it is already associated with another listing, workspace, or account. This can happen even when you are the website owner. Common causes include: - The website was previously added by you or a teammate. - The domain is listed under another Search Atlas workspace. - You are adding a different version of the same site, such as www versus the root domain. - An old or duplicate listing still exists. 🧭 Check your existing listings 1. Open Website Studio from the left sidebar, or go to /website-studio. 2. Review your website listings and search for the domain. 3. Check common variations, including the root domain, www version, HTTP, and HTTPS. 4. Open the existing listing to confirm whether it is the site you want to manage. ✅ Confirm the correct website Compare the listing with your website’s address. Make sure you are not trying to add a subdomain, folder, or alternate URL as a separate website when it belongs to an existing domain listing. If the existing listing is in your workspace, continue using it instead of creating another one. This keeps your website data and settings together. 🔄 Request a listing correction If the site belongs to you but is attached to another workspace or account, do not create a duplicate listing. Prepare the following information: - The exact website domain and URL variation. - The Search Atlas workspace where you want to manage it. - Proof that you control the website, if requested. - The name or location of any existing listing you found. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. ⚠️ Avoid duplicate listings Do not repeatedly retry the same domain or create multiple variations to bypass the conflict. Duplicate entries can split your website data and make ownership harder to resolve. Use one accurate listing and ask our team to review ownership when the website is already claimed elsewhere.

🛠️ Resolve Unusable Publication Sites

🔍 Why publication stops A Zia Tile article can remain unassigned when its selected site is no longer usable. Common reasons include no active publication, a non-US publication, a farm-listed domain, or a failed validation rule. The assigner does not automatically replace a site selected in Publication Notes. This prevents Search Atlas from changing your publishing decision without approval. The article is therefore skipped during each hourly assignment run until a replacement is chosen. 📋 What the replacement options mean Suggested sites come from the same assignment engine used for normal placement. Each option meets the applicable requirements, including: - The minimum ordered DA - DR and organic traffic requirements - The 2.5x price limit compared with the ordered DA - QP quality requirements - Your account’s rejection history Options may have a DA above the ordered range. This is expected: the price limit is the effective ceiling, and additional authority can be beneficial. Sites are listed from least used to most used where possible. Topic evidence shown beside a site is a preference signal, not a requirement. It is based on reviewing the site’s existing article titles. ✅ How to resolve the articles 1. Review each article with an unusable current pin. 2. Compare the suggested domains, DA, price, prior usage, and topic evidence. 3. Choose one option for every article, or suggest another suitable site. 4. Provide the article ID and your choice, such as 200586 → 2. 5. Wait for the approved reassignment and updated Publication Note before the next assignment run. For multiple orders, include the order number and article ID to avoid confusion. You can choose different sites for different articles, even when they share the same order. 🔁 What happens after approval After your choices are confirmed, the articles are reassigned and their Publication Notes are updated. This prevents the hourly cron or cascade process from moving them again. Articles should then become eligible for normal placement, provided the replacement site remains active and passes validation. 💡 Prevent future delays - Review Publication Notes before submitting or pinning an article. - Avoid selecting sites without an active publication. - Confirm that the publication is US-based when that rule applies. - Recheck saved sites if an article remains unassigned across multiple runs. - Respond with one clear replacement choice per article. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Purge Ghost Routes and Rebuild

🧭 What this process removes A backend purge removes unwanted ghost, orphaned, staging, and corrupted routes from the website data and cache layers. This can include duplicate URL variants, encoded characters, outdated imported pages, and routes that no longer belong to the current site. A clean rebuild then recreates the website using the approved pages and settings. This helps prevent removed routes from returning after publishing or cache refreshes. 🔎 Prepare the route list 1. Collect every unwanted URL and variant in one list. 2. Include differences in capitalization, trailing slashes, query parameters, encoded characters, and alternate paths. 3. Mark each route as ghost, orphaned, staging, corrupted, or otherwise invalid. 4. Confirm which pages and assets must remain live. Include the complete URL, not only the visible page name. Encoding garbage and duplicate variants can otherwise be missed during cleanup. 🧹 Request a backend purge Backend purge requests are handled by the Search Atlas team because they can affect stored site data, cache layers, and published content. Provide the complete route list and clearly request both actions: purge the invalid routes and start a clean rebuild. Do not repeatedly republish while the purge is being processed. New publishing activity can recreate routes or make verification harder. 🏗️ Start the clean rebuild After the purge is confirmed, open Website Studio from the left sidebar. Review the remaining pages and site settings, then use the appropriate site workflow, such as Import Site or Generate PPC Site. Submit the rebuilt site only after confirming that unwanted routes are excluded. Publishing and cache cleanup are separate steps. A page may appear unchanged temporarily if a browser, edge, or website cache still contains an older version. ✅ Verify the result 1. Check the previously invalid URLs and all listed variants. 2. Confirm that valid pages still load and that removed routes no longer resolve to published content. 3. Refresh the relevant report data from Reports in the left sidebar, then review the updated results. 4. Test again after cache propagation is complete, using a private browser window when possible. If a removed route returns, capture the exact URL, when it returned, and the action that preceded it. This information helps identify whether the route was recreated by an import, republish, redirect, or external cache. 💡 Prevent routes from returning - Use one approved source of truth for pages and imports. - Remove obsolete pages from the source before rebuilding. - Keep staging and production content separate. - Review redirects, internal links, sitemaps, and integrations for references to deleted routes. - Allow each purge or rebuild to finish before starting another publish action. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Resolve Order Alternative Disputes

📋 Understand order alternatives If a publication or placement cannot fulfill your order, Search Atlas may offer alternative options. An alternative is not automatically fulfilled unless it is selected and confirmed for the affected order item. If you provided alternatives for both items, review each item separately. One accepted alternative does not confirm or replace the other item. 🔍 Review your order 1. Open the order from the order notification or select Go to Orders. 2. Open the specific order and review each item’s status. 3. Check whether the original publication was rejected, an alternative was selected, or the item is still awaiting fulfillment. 4. Compare the selected publication, service, price, and fulfillment status with what you purchased. 🔄 Select an alternative When an item is rejected and alternatives are available, open the alternatives list for that item. Review the publication details and any price difference before selecting an option. - Select an alternative for every affected item. - Confirm your selection when prompted. - Return to the order and verify that the selected alternative appears on the item. - Do not assume that opening or previewing an alternative completes the selection. If no alternatives appear, the item may not currently have an eligible replacement. Record the order number and item details before contacting support. ✅ Confirm fulfillment After selecting an alternative, monitor the item status in the order. Keep the order confirmation, selected publication, price details, rejection notice, and any fulfillment updates. These details help distinguish an unfulfilled item from an item that was completed with an approved alternative. ⚖️ If the delivered item differs If you received something different from the confirmed order, do not place a duplicate order. First verify the item status and selected alternative, then document the difference clearly. - Record the order and item identifiers. - Note the original publication and the confirmed alternative. - Describe what was delivered and what was missing. - Include relevant status messages or screenshots from the platform. Submit these details through the platform chat so the team can review the order history and fulfillment record. Avoid making repeated changes while the issue is under review. 💬 Get help with a dispute For unresolved fulfillment, missing alternatives, incorrect order information, or payment-related questions, provide the order number and explain the issue for each item separately. The support team can review the available order records and clarify the next step. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📅 Content Planner Troubleshooting

This article covers: - Content Planner scheduling - Calendar visibility - Content brief generation - Publishing workflows - CSV imports - Team collaboration Content Planner helps teams: - Organize publishing schedules - Generate SEO content briefs - Coordinate workflows - Manage topic planning across projects and campaigns Content Planner integrates with: - Keyword Research - Supported CMS connections (e.g., WordPress) - AI Brief Generation - Project-level permissions Many issues are caused by: - Project mismatches - Missing metadata - Formatting errors - Synchronization delays ⚠️ Known Limitation: Direct publishing from Content Genius/Content Planner to Website Studio sites is not currently available. This integration is in development with no confirmed release date. In the meantime, you can publish through a connected WordPress CMS or manually copy content into your Website Studio site. ⚠️ Error 1: Scheduled content items are not appearing on the calendar What's happening Content Planner displays content items based on: - the currently selected project - visibility filters - and active calendar views. Items created under different projects remain hidden unless the correct project is selected. The Content Planner shows the content of the one project/plan currently selected, not all projects at once. Steps to try 1. Confirm the correct project is selected in the Project dropdown. 2. Refresh the calendar page. 3. Check whether date filters are hiding the content item. 4. Verify the item was saved successfully. 5. Confirm the content item has a valid publish date assigned. Items without an assigned publish date will not appear in monthly or weekly calendar views. Switch to List view to locate undated items and assign a date. 6. Switch between monthly, weekly, and list views — some items may only appear in list view if they lack a publish date or if the calendar view is filtering by a date range that excludes them. 7. Check whether the item was accidentally archived or deleted. 8. Confirm the item belongs to the current workspace/team. 9. Contact support if calendar items disappear across all projects. Important Notes - Project filtering is the most common cause of missing calendar items. When the wrong project is selected, items created in other projects will remain hidden until you switch projects. The Content Planner shows only the currently selected project. - Items are isolated by project structure intentionally to keep workspaces organized and prevent cross-project clutter. ⚠️ Error 2: Content brief generated from the planner is missing or empty What's happening Content briefs rely on: - associated target keywords - keyword data availability - and successful AI brief generation. Items without target keywords cannot generate meaningful briefs. Steps to try 1. Open the calendar item settings. 2. Confirm a Target Keyword is assigned. 3. Use a keyword with measurable search data. 4. Click Generate Brief again after saving the keyword. 5. Wait 30–60 seconds for generation to complete. 6. Refresh the item after generation finishes. 7. Avoid extremely broad or unsupported keywords. 8. Test the keyword in Keyword Research first. 9. Regenerate the brief using a more specific keyword phrase. 10. Contact support if briefs remain empty despite valid keywords. Important Notes - Brief generation depends heavily on keyword quality. - Missing keyword data produces incomplete or blank briefs. ⚠️ Error 3: Published content is not being automatically marked as complete What's happening Content Planner does not always detect publishing automatically unless: - CMS Integration is connected - synchronization is enabled - and the publish event is recognized correctly. Manual publishing outside integrated workflows may not sync automatically. Steps to try 1. Manually update the item status: Status → Mark as Published. 2. Check whether CMS Integration is enabled. 3. Go to: CMS Integration → Settings → Sync to Content Planner. 4. Confirm the connected CMS matches the project domain. 5. Refresh the Content Planner after publishing. 6. Verify the published URL matches the planned content URL. 7. Reconnect the CMS integration if sync appears broken. 8. Wait a few minutes for synchronization delays. 9. Avoid duplicate calendar entries for the same URL. 10. Contact support if automatic sync never updates published items. Important Notes - Manual publishing workflows require manual status updates unless sync is enabled. - CMS synchronization can take several minutes. ⚠️ Error 4: Content Planner shows a duplicate topic conflict warning What's happening The planner compares: - target keywords - semantic similarity - and planned topics to prevent content cannibalization. Similar keywords trigger warnings automatically. Steps to try 1. Click View Conflicting Item to inspect the overlap. 2. Compare the keyword intent between both items. 3. Determine whether the topics truly compete. 4. Merge duplicate content plans if appropriate. 5. Differentiate the angle or search intent if keeping both. 6. Use more specific target keywords. 7. Add modifiers to distinguish the content: - guide - comparison - local - pricing - tutorial - etc. 8. Review whether one item is outdated or unnecessary. 9. Ignore the warning only if the content serves different intents. 10. Re-run keyword validation after adjusting the topic. Important Notes - Duplicate warnings are preventive, not blocking errors. - Similar keywords do not always equal cannibalization. ⚠️ Error 5: Team member cannot see the Content Planner items created What's happening Content Planner visibility depends on: - project permissions - workspace access - and team role settings. Users without access to the specific project or workspace will not see items created within it, even if they belong to the same organization. Steps to try 1. Confirm the team member has been added to the correct project. 2. Verify their assigned role grants Content Planner access. 3. Ask the team member to switch to the correct project in the Project dropdown. 4. Refresh the calendar after permission changes are applied. 5. Re-invite the team member if their account was recently added. 6. Confirm the items were not accidentally created in a personal or private workspace. 7. Contact support if access issues persist after role adjustments. Important Notes - Project and workspace permissions are the primary driver of visibility issues for team members. - Role changes may take a few minutes to propagate. ⚠️ Error 6: WordPress shows as connected but publishing fails with a "website not connected" error What's happening The WordPress integration can appear connected in the interface while the underlying credentials or authentication tokens have expired or become invalid. This causes publish attempts to fail with a "website not connected" error even though the connection status looks healthy. Steps to try 1. Disconnect the WordPress integration from Account Menu → Settings → CMS Connectors. 2. Reconnect the WordPress site and re-authenticate. 3. Verify CMS credentials (username, application password, or API token) are still valid in WordPress. 4. Confirm the WordPress site URL matches the project domain. 5. Check that the WordPress user account has publishing permissions. 6. Retry the publish action after reconnecting. 7. Contact support if the issue persists after reconnecting the integration. Important Notes - A visually connected WordPress integration does not always mean the credentials are still valid. - Disconnecting and reconnecting forces a fresh authentication and resolves most "website not connected" errors. ⚠️ Error 7: Publish action hangs or takes longer than expected What's happening Publish actions can take several minutes depending on: - CMS response times - platform-level processing delays - and synchronization queues. If publishing to a Website Studio site appears to hang or takes longer than expected, this may be a platform-level delay. Wait several minutes and check the published URL before retrying, as duplicate publish attempts can compound delays. Steps to try 1. Wait several minutes before retrying — the publish may still be processing. 2. Check the published URL directly to confirm whether the content actually went live. 3. Avoid clicking Publish multiple times, which can create duplicate publish attempts. 4. Refresh the Content Planner to see if status has updated. 5. Verify the CMS connection is healthy in CMS Integration settings. 6. If the publish still appears stuck after 10+ minutes, mark the item manually using Status → Mark as Published once you confirm the URL is live. 7. Contact support with the item ID if the publish never completes. Important Notes - Publish delays are most often platform-level and resolve without intervention. - Always verify the live URL before retrying to avoid creating duplicate posts. ❓ FAQ: Can I publish Content Planner or Content Genius articles directly to Website Studio? Not yet. Direct publishing from Content Planner or Content Genius to Website Studio sites is not currently available. This integration is in development with no confirmed release date. Available alternatives: - Publish through a connected WordPress CMS if your project uses WordPress. - Manually copy the finalized content from Content Genius/Content Planner into the Website Studio editor. - Track publishing status manually in Content Planner by setting Status → Mark as Published once the article is live on your Website Studio site. If direct Website Studio publishing is critical to your workflow, contact support to be notified when the integration becomes available.

📋 Check PR Network Sites Before Ordering

🔍 Why Check the Site List First? Before placing a PR distribution order, it is important to know exactly which websites and URLs will publish your press release. Reviewing the site list in advance helps you confirm that the network aligns with your target audience, niche, or geographic focus — and avoids any surprises after purchase. 📋 What Is a PR Network Site List? Each PR distribution network available in Search Atlas publishes your press release to a defined list of partner sites. Knowing which sites are included before you order helps you evaluate whether the placements match your campaign goals, target audience, and geographic focus. The specific URLs and domain names included in any network are subject to periodic updates as partner sites are added or removed to maintain quality and relevance. 🛠️ How to Get the Full Site List Before Ordering 1. Log in to your Search Atlas account. 2. Navigate to the PR Distribution section from your dashboard. 3. Identify the PR network you are considering. 4. If the full site list is not immediately visible on the network's detail page, contact the support team via the chat widget to request the complete list of included sites before placing your order. Always review the site list before confirming your order to make sure the placements match your campaign goals. 💡 Tips for Evaluating a PR Network Site List - Check domain relevance: Look for sites that cover topics related to your industry or geographic target. - Look for niche alignment: Match the network's focus (e.g., broadcast, tech, regional) to your announcement type and intended audience. - Note the total site count: More placements generally mean broader reach, but quality matters more than quantity. ❓ Frequently Asked Questions Can I request a custom site list? At this time, site lists are predefined per network and cannot be customised individually. Contact the support team via the chat widget for guidance on which network best fits your needs. Do site lists change over time? Yes. Search Atlas periodically updates network site lists to maintain quality standards. The list shown at the time of your order reflects the most current available placements. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ Removing Hero Overlay and Resizing Your Logo

🔍 Overview In Website Studio, your hero section may display a dark overlay (also called an image scrim) over your background image, and your logo may appear smaller than you'd like. This article walks you through how to remove the overlay and resize your logo so your homepage looks exactly the way you want it. 🗑️ Removing the Dark Overlay from Your Hero Image The dark overlay is a semi-transparent layer applied on top of your hero background image. Follow these steps to remove it: 1. Open Website Studio from the left-hand navigation menu. 2. Select your website and navigate to the Home page. 3. Click on the Hero section to open its settings panel. 4. Look for the Overlay or Image Scrim toggle in the settings panel. 5. Toggle the option off to remove the dark overlay from your hero image. 6. Click Save or Publish to apply your changes. Important: After removing the overlay, make sure to save your page before navigating away. If you leave the page without saving, the overlay may be re-applied automatically. Always confirm your changes are saved before moving to another section. 📐 Resizing Your Logo on the Home Page If your logo appears too small in the hero section or header, you can increase its size directly in Website Studio: 1. In Website Studio, open your Home page in the editor. 2. Click on the logo element in the hero section or header to select it. 3. In the settings panel on the right, locate the Logo Size or Width slider. 4. Drag the slider to the right or enter a larger value to increase the logo size. 5. Preview the result on both desktop and mobile views to ensure the logo looks good across all screen sizes. 6. Click Save or Publish to apply your changes. Tip: If your logo appears blurry after resizing, upload a higher-resolution version of your logo file (PNG or SVG recommended) through Agency Settings (Logo) → Upload Agency Logo before adjusting the size. ⚠️ Common Issues and How to Fix Them - The overlay comes back after saving: This can happen if you navigate away too quickly. Save your changes, then refresh the page to confirm the overlay has been removed successfully before closing the editor. - Logo changes are not saving: If your logo size edits are not persisting, try clearing your browser cache and making the adjustment again. Ensure you click Save before leaving the page. - Logo is hard to read on the hero image: If your logo blends into the background after removing the overlay, consider uploading a version of your logo with a contrasting color or a transparent background. You can also add a subtle drop shadow through the logo element settings. - Edits on duplicated pages overwrite the original: Avoid editing both a duplicated page and the original at the same time. Make all changes on one page, save, and then proceed to the other to prevent conflicts. ✅ Best Practices for Your Hero Section - Always preview your page on both desktop and mobile after making changes to the hero section. - Use high-resolution images (at least 1920×1080 px) for hero backgrounds to avoid pixelation. - Keep your logo file in SVG or PNG format with a transparent background for the best results at any size. - Save frequently while editing to prevent losing your work. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Custom JavaScript Not Showing on Live Site

🔍 Overview Custom JavaScript added through your site's custom code settings should appear in your live site's page source after publishing. If your code is not showing up, a few common causes are usually responsible. This article walks you through general troubleshooting steps to try before escalating to the support team. ✅ Step 1: Confirm the Code Was Saved and Published The most frequent cause of missing custom code is an incomplete save or publish action. 1. Navigate to the custom code or custom scripts section of your platform dashboard. 2. Verify your JavaScript code is present in the correct field. 3. Save any unsaved changes. 4. Publish or apply the changes to push them to your live site. 5. Wait 1–2 minutes, then hard-refresh your live site (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) and check the page source again. 🗄️ Step 2: Clear Your Cache Caching at multiple levels — browser, server, or CDN — can prevent updated code from appearing immediately in your live site source. - Browser cache: Perform a hard refresh as described above, or open your site in a private/incognito window. - Server or CDN cache: If your site uses a CDN (such as Cloudflare) or a server-level caching plugin, purge the cache from that service's dashboard and check again. - Platform cache: If your Search Atlas-connected site has a caching layer, clear it and re-check the live source. 📋 Step 3: Check That Your Code Is Valid JavaScript Invalid or malformed JavaScript can cause the code block to be stripped or silently ignored during publishing. - Make sure your code does not contain unclosed tags, mismatched brackets, or syntax errors. - If you are embedding a third-party script, ensure you are pasting the full snippet exactly as provided, including any required opening and closing <script> tags. - Test your snippet in a JavaScript validator or your browser's developer console before adding it to the platform. 🔒 Step 4: Check for Security or Content Policy Restrictions Some hosting environments and security configurations block the injection of inline scripts or scripts from external domains. This is enforced by the server or CDN — not by Search Atlas — and can silently prevent custom code from rendering. - Review your site's Content Security Policy (CSP) headers to confirm external script sources are allowed. - If you are using a security plugin or firewall (such as Wordfence or Sucuri), check whether it is filtering custom script injections. - Contact your hosting provider if you suspect server-level policies are blocking the code. 📩 Still Not Showing? Escalate to Support If you have worked through the steps above and your custom JavaScript is still not appearing in your live site source, the issue may require investigation by the Search Atlas team. To help us resolve it quickly, please have the following ready before reaching out: - The exact JavaScript snippet you are trying to add. - The URL of the live page where the code should appear. - A description of which step you completed and what result you observed. - Any error messages shown in your browser's developer console (right-click the page → Inspect → Console tab). - The timestamp of when you last saved and published your changes. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix AI Title Tags Exceeding 60 Characters

Overview Search Atlas uses AI to generate SEO title tags across several tools. By default, best-practice title tags should stay within 50–60 characters to avoid truncation in Google search results. If your AI-generated titles are consistently longer than this, this article explains how to address the length issue and how to request subscription changes if needed. How to Check and Fix Title Tag Length 1. Locate the title tag for the relevant page inside your Search Atlas project and review its character count. If it exceeds 60 characters, it needs to be revised. 2. Edit the title tag directly in the field provided and shorten it to 60 characters or fewer before saving. 3. If you want the AI to regenerate a title tag, open the relevant tool and include a clear instruction specifying your desired character limit in the prompt. Reviewing and manually editing the output before publishing is recommended to ensure the length meets your requirements. 4. After updating, verify the corrected title before publishing by pasting it into any free character-counter tool to confirm the length. Tips to Prevent Oversized Title Tags - Include a character limit in your prompt. Specify your maximum character count when generating title tags via any AI tool in the platform. - Review before publishing. Paste your title into any free character-counter tool to confirm length before going live. - Shorten long keywords. If your primary keyword is naturally long, consider a shortened variation that still captures search intent. Subscription Cancellation If you need to cancel your subscription or make changes to your billing, our support team can process the cancellation or any billing adjustments on your behalf. To get help quickly, use the chat widget in the bottom-right corner of the platform and type human teammate to connect with a team member. When reaching out, have the following ready to help the team act quickly: - Your account email address - The name of your Search Atlas project or workspace - The reason for cancellation (e.g., AI outputs not meeting expectations, credit usage concerns) - Any relevant dates or billing period details If you believe credits were used on AI outputs that did not meet your needs, mention this when you contact support so the team can review your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗞️ View PR Network Sites Before Placing an Order

📋 Overview Before placing a PR order, you can browse the complete list of websites included in any PR network directly inside the publication selection interface. You do not need to place an order first — the site list is available at the point of selection, so you can review every URL and make an informed decision before you commit. 🔍 How to View the Website List for a PR Network 1. Log in to Search Atlas and navigate to the PR distribution section from the left sidebar. 2. On the publication selection screen, locate the PR network you want to review — for example, Canadian Broadcast News Network. 3. Click the network name or the View Sites / See Included Sites button next to the listing. This expands or opens a panel showing the full list of websites and their URLs that belong to that network. 4. Scroll through the list to review each individual domain and URL included in the network. 5. Once you have confirmed the sites meet your requirements, proceed to place your order as normal. 💡 What You Will See in the Site List The expanded site list for a PR network typically includes: - Website name — the publication's display name. - URL — the exact domain where your press release will be published. - Domain metrics — authority or traffic indicators where available, to help you assess publication quality. This information is visible before any payment is made, so you can compare networks and choose the one that best fits your campaign goals. ⚠️ Important Clarification: Pre-Order vs. Post-Publication Access Some customers are directed to the post-publication dashboard to find site details after an order is complete. That dashboard shows where your content was published after the fact. It is not the right place to research sites before you order. The correct place to view included sites before purchasing is the publication selection interface during the ordering flow, as described in the steps above. Always review the site list at that stage so you know exactly what you are buying. 🛠️ Troubleshooting If you cannot see the site list or the expand option does not appear, try the following: - Refresh the page and navigate back to the publication selection step. - Clear your browser cache and try again in a clean session. - Try a different supported browser such as Chrome or Firefox. - Make sure you are fully logged in and have not timed out of your session. If the site list is still not visible after these steps, contact our support team for help. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix URL Rewrite and Social Share Thumbnail Mismatch

Overview When sharing a Website Studio project URL on social media, the preview thumbnail may display an incorrect domain (for example, juicynote.com instead of thejuicynote.com). In some cases, this misconfiguration may also be associated with duplicate form submissions. Both issues are related to URL rewrite and domain configuration in your Website Studio project. What Causes This Issue A URL rewrite or custom domain mapping that is not applied consistently across your project can result in a mismatch between the domain visitors see in a social media thumbnail and the domain your project actually lives on. Social platforms read Open Graph (OG) metadata to generate thumbnails, and if that metadata still references an old or alternate domain, the wrong domain may appear in previews. Duplicate form submissions may also occur when more than one domain variant is active for the same project, though the exact mechanism can vary depending on your specific setup. What to Do Because the specific settings and steps needed to resolve URL rewrite and social share thumbnail issues depend on how your Website Studio project is configured, our support team will need to review your setup directly to identify the correct fix. When contacting support, please have the following ready: - The name of the affected Website Studio project - The domain or domains involved (e.g., the incorrect domain appearing in thumbnails and the correct intended domain) - Any error messages or unexpected behavior you have observed, including whether you are seeing duplicate form submissions - The URL you are sharing on social media and the platform(s) where the incorrect thumbnail appears - The approximate date and time the issue started If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Recover Deleted AI Projects and Fix Geo-Tagging

Overview This article covers two issues that may occur in Content Genius: accidentally deleting an active AI project and being unable to click the geo-tagging feature. It explains what to expect in each case and how to escalate effectively to our support team. Understanding AI Project Deletion Content Genius does not currently offer a confirmed self-serve restore option for deleted AI projects. Once a project is deleted, its generated content, settings, and associated artifacts may no longer be accessible from your workspace. What to Do After an Accidental Deletion Deleted project recovery requires investigation by our support team. To give our team the best chance of looking into recovery options, please connect with us as soon as possible and have the following information ready: - The exact name of the deleted project - The approximate date and time of the deletion - Your account email address - Any exported or saved copies of the project content you may already have The sooner you report the deletion, the sooner our team can investigate your specific case. Content Genius Geo-Tagging Bug Some customers report that the geo-tagging option inside Content Genius is unresponsive — clicking it produces no action or does not open the expected selector. If you are experiencing this, please connect with our support team and have the following ready: - The name of the project where the geo-tagging option is unresponsive - The exact behavior you are seeing (for example, no response on click, or a selector that opens but cannot be interacted with) - The date and time you first noticed the issue - Your browser name and version If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Atlas Brain Canonical Tag Configuration and Override Procedures

Why Atlas Brain May Not Apply Your Canonical Tag Request When Atlas Brain does not apply a canonical tag change, it is typically because the request could not be mapped to a specific, actionable change for the pages in question. This is not necessarily a sign that the feature is unavailable — it may mean the request needs to be clarified or completed manually through Website Studio. Common reasons a canonical tag request may not go through include: - The request did not clearly specify which pages or URLs should be updated. - The pages in question may already have canonical values that the system is managing. - The request involved a large or complex set of pages that Atlas Brain could not resolve without more specific input. How to Manage Canonical Tags in Website Studio If Atlas Brain was unable to apply your canonical tag change, you can make the update directly in Website Studio. Because the specific steps depend on your account's interface version, we recommend doing the following: 1. In the left sidebar, click Website Studio (/website-studio). 2. Locate the page or pages where you want to set or update the canonical tag. 3. Look for the SEO or metadata settings area within the page editor for that page. 4. Find the field related to the canonical URL and enter the value you want to apply. 5. Save your changes and verify the canonical tag is reflected as intended. If you are unsure where the canonical tag settings are located within your specific interface version, or if the field does not appear to be editable, our support team can guide you to the correct location for your account. What to Have Ready When Contacting Support If you are unable to locate the canonical tag settings or Atlas Brain continues to not apply your request, please have the following information ready so our team can assist you efficiently: - The name of the project or website in Website Studio. - The specific pages or URLs where you want canonical tags set or updated. - The exact canonical URL value you want applied. - Any message or response Atlas Brain returned when you submitted your request. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚠️ Content Rewriting — Step 1 and Step 2 Panels Go Blank After Clearing Original Content

A display bug in the Content Rewriting feature of Content Genius caused both panels to appear blank after clearing the original content in Step 1. No content is ever lost — the fix is now live, and a hard refresh is all you need to resume your workflow. 🔍 What's Happening After a successful rewrite, deleting or clearing the original content in Step 1 and then clicking into Step 2 causes both panels to go blank, making the rewritten result appear to disappear. Clicking back to Step 1 may also cause the rewritten content to reappear in Step 2 unexpectedly. This is a display and rendering issue only — no content is deleted or permanently lost at any point during this interaction. 🛠️ Workaround Steps 1. Copy or save your rewritten content from Step 2 before clearing Step 1. Do not delete the original content until you have saved the rewritten result. 2. If both panels are already blank, click back to Step 1 — your rewritten content should reappear in Step 2. 3. Perform a hard refresh of your browser to pick up the live fix and permanently resolve the issue: - Windows / Linux: Ctrl+Shift+R - Mac: Cmd+Shift+R After a hard refresh, the blank-panel behavior will no longer occur and Content Rewriting will work as expected. 📡 Engineering Status This bug has been identified, investigated, and resolved. The fix is live in the current version of Search Atlas — no further action is required beyond performing a hard refresh of your browser to load the updated version. 📞 When to Contact Support If blank panels persist after performing a hard refresh, reach out to the Search Atlas support team. Include a brief description of the steps you took and, if possible, a screenshot of what you are seeing so the team can investigate promptly. 🌀 This display issue is fully resolved — a hard refresh restores your Content Rewriting workflow immediately. If blank panels continue after refreshing, our support team is ready to help.