Troubleshooting: Press Release Issues

⚡ Fix Digital PR Inbox Syncing Delays and Missing Emails

Overview If your Digital PR outreach inbox is showing message counts but no emails are appearing, or you see an indication that your mailbox is still syncing with Search Atlas, this article explains why this happens and what to expect. What You Might Be Seeing - Your inbox shows no email content despite appearing active. - Message counts appear in the sidebar, but clicking the inbox reveals no emails. - A notice indicates that email syncing is in progress. - Sent or received emails from outreach campaigns are not visible. Why This Happens When you connect a mailbox to the Digital PR Campaigns inbox for the first time — or after reconnecting a previously unlinked mailbox — Search Atlas must sync your email history from your mail provider. Depending on the volume of emails in your account, this process can take some time. During this window, the inbox UI may display counts or labels before the actual content has loaded. What to Do 1. Wait and refresh. After connecting your mailbox, give it some time and then refresh your browser. Syncing delays are expected behavior and typically resolve on their own once the process completes. 2. Check that your mailbox is properly connected. Confirm that the email account you intend to use for outreach is connected to your Search Atlas account and is not showing a connection error. 3. Confirm your campaign has a linked email account. Verify that your outreach campaign has an associated email account configured, as campaigns without a properly linked mailbox may contribute to inbox display issues. When to Escalate If you have waited a reasonable amount of time and your inbox still shows no emails despite having an active mailbox connection, please reach out to our support team. To help us investigate quickly, have the following ready: - The email address of the connected mailbox experiencing the issue - The name of the affected outreach campaign - A description of what you see in the inbox (e.g., message counts with no content, any on-screen notice text) - Approximately when 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.

🛠️ Fix Press Release Link Popup Positioning

🔗 What causes the popup issue? When you add or edit a hyperlink in a press release, the link window may appear partially off-screen. This can happen when the editor is scrolled, the browser window is resized, or the browser zoom level is changed. 📍 Open the press release editor 1. Open Authority from the left sidebar. 2. Select PR Distribution. 3. Choose New Release or Resume to open an existing draft. 🛠️ Try these quick fixes 1. Scroll the editor back to the section containing the text you want to link. 2. Move the page slightly upward or downward so the editor toolbar is visible. 3. Reduce your browser zoom to 90% or 80%, then try opening the link tool again. 4. Maximise the browser window and make sure your device display is not using an unusually large scaling setting. 5. Close and reopen the press release editor, then retry the link tool. 6. If the popup still opens off-screen, refresh the page and reopen the draft from Resume. ✏️ Add the hyperlink 1. Highlight the words you want to link. 2. Select the link or URL tool in the editor toolbar. 3. Enter or paste the destination URL into the popup. 4. Apply or save the link, then confirm that the linked text displays correctly. ✅ Check your link before publishing - Confirm the URL starts with https:// when required. - Check that the link opens the intended page. - Review the surrounding text for formatting issues. - Save the draft before leaving the editor. 💬 Need more help? If the hyperlink popup remains unusable after these steps, note your browser, screen size, zoom level, and the actions that caused the issue. 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.

🛠️ Troubleshoot PR Distribution and CloudStacks Issues

🔍 Overview If you are experiencing issues with PR Distribution or CloudStacks in Search Atlas, this guide walks you through the most common problems and how to resolve them quickly. Follow the steps below before reaching out to support. ⚙️ Common PR Distribution Issues and Fixes PR Distribution allows you to publish and syndicate press releases across a network of sites. If something is not working as expected, try the following steps: 1. Check your submission status. Navigate to your PR Distribution dashboard and confirm whether your press release shows a status of Pending, Processing, or Failed. A Pending status means it is queued and will process shortly. 2. Review your content for compliance. Press releases that contain prohibited content, broken links, or formatting errors may be rejected. Re-read the content guidelines and ensure your release meets all requirements before resubmitting. 3. Verify your account credits or plan limits. Press release distribution draws from your shared Hyperdrive Credits (HDC) balance — if that balance is exhausted, new submissions will be blocked. Go to the Avatar Menu (👤) (Avatar Menu (👤), top-right) → Billing → Plans & Top-ups to check your current Hyperdrive Credits usage and balance. 4. Clear your browser cache and retry. Occasionally, stale cache data can cause submission forms to behave unexpectedly. Clear your cache, refresh the page, and attempt your submission again. 5. Check for platform status updates. If multiple submissions are failing at the same time, there may be a temporary service disruption. Check the Search Atlas status page or the in-app notification banner for updates. ☁️ Common CloudStacks Issues and Fixes CloudStacks is a powerful link-building feature that creates a network of cloud-based properties pointing to your target URLs. Here are the most common issues and how to address them: 1. Stack not building or stuck in progress. If your CloudStack has been stuck in the Building state for more than 24 hours, first check whether your target URL is accessible and returns a 200 status code. Broken or redirected URLs can stall the build process. 2. Properties not indexed. Newly created cloud properties can take several days to be indexed by search engines. This is normal behaviour. Allow 5–10 business days before expecting indexation results. 3. Incorrect target URL submitted. If you submitted the wrong URL for a CloudStack, contact support immediately. Depending on the build stage, the team may be able to update the target URL before the stack is fully deployed. 4. Stack shows as complete but links are not visible. Confirm you are viewing the correct project in your dashboard. Use the filter or search function to locate the specific stack by name or date created. If the stack report appears blank, try refreshing the page or switching browsers. 5. Duplicate stack submission. Submitting the same URL multiple times does not always improve results and may affect your link profile. Review your active stacks before creating a new one for the same target URL. 🔗 Issues Affecting Both PR Distribution and CloudStacks If you are experiencing problems with both features at the same time, the issue is likely related to one of the following: - Account or billing issue. A lapsed subscription or failed payment can restrict access to multiple features simultaneously. Go to the Avatar Menu (👤) (Avatar Menu (👤), top-right) → Billing to verify your subscription status and update your payment method if needed. - Browser or device compatibility. Both features require a modern browser. Ensure you are using the latest version of Chrome, Firefox, Edge, or Safari. Disable browser extensions that may interfere with the platform, such as ad blockers or script blockers. - Session or login issue. Log out of your Search Atlas account, clear your cookies, and log back in. This resolves many unexpected UI or submission errors. - API or integration conflict. If you are using the Search Atlas API or a third-party integration, verify that your API key is valid and that your requests are formatted correctly according to the latest API documentation. 📋 Before You Contact Support To help our team resolve your issue as quickly as possible, gather the following information before starting a chat: - The name or ID of the affected PR submission or CloudStack - The target URL associated with the issue - A description of what you expected to happen versus what actually happened - Any error messages you saw on screen - The date and time you first noticed the issue 💬 Still Need Help? If the steps above did not resolve your issue, our support team is ready to assist. 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.

📰 Authority Building — PR Distribution

This article covers: - press release submission - distribution workflow errors - company profile configuration - AI-generated PR content - outlet reporting - distribution credits - and post-submission limitations. Authority Building distribution workflows involve: - validation systems - asynchronous distribution queues - external publisher synchronization - and outlet-specific formatting pipelines. Because multiple systems participate in the distribution process, delays or validation failures may occur before a press release reaches publication status. ⚠️ Error 1: "Submit for Distribution" button is greyed out What's happening The distribution system requires all mandatory fields before submission becomes available. Even one incomplete or invalid field prevents activation of the submission button. Steps to try 1. Open the press release editor in a supported browser (Chrome is recommended) and review all sections carefully. 2. Confirm all required fields are completed: - Headline - Body - Summary - Company Name - Publish Date - Publish Time. 3. Ensure the press release body meets the editor's minimum word count (confirm the current minimum against the in-app validation message). 4. Confirm the summary is within the editor's word cap (confirm the current cap against the in-app validation message). 5. Check for validation warnings highlighted in red. 6. Verify the distribution date is not in the past. 7. Remove unsupported special characters from fields if validation still fails. 8. Save the draft and refresh the page. 9. Contact support if the submission button remains disabled despite all fields being completed. Important Notes - Hidden validation errors are often caused by formatting issues such as unsupported characters, stray HTML, or trailing whitespace. - Saving the draft usually refreshes validation states. ⚠️ Error 2: Press release submitted but status stays on "Processing" for more than 2 hours What's happening The backend distribution system may have encountered: - silent validation failures - queue delays - or incomplete company profile data. The press release remains in a pending state until validation succeeds. Steps to try 1. Go to: Left Sidebar → Authority Building → PR Distribution → [your PR] → Status 2. Refresh the status page after several minutes. 3. Click Retry Distribution if available. 4. Review your company profile completely. 5. Ensure all required company fields are populated: - company name - address - phone - website - country code. 6. Verify the summary is within the editor's word cap. 7. Confirm there are no placeholder values left in the PR. 8. Avoid duplicate submissions while processing is active. 9. Wait several additional queue cycles during high-traffic periods. 10. Contact support if processing remains active longer than 2 hours. Important Notes - Backend validation failures are not always surfaced immediately. - Retry Distribution often clears transient queue issues. ⚠️ Error 3: Distribution report shows 0 outlets after 24 hours What's happening A press release may have been submitted successfully but never actually distributed. "Submitted" status does not always mean: - distributed - published - or syndicated. Steps to try 1. Open the distribution status page. 2. Verify the status shows: - Distributed - Published - or Completed. 3. If the status only says Submitted, the PR likely never entered the distribution network. 4. Refresh the distribution report after several hours. 5. Confirm your company profile passed validation. 6. Check whether the PR was rejected silently. 7. Retry the distribution if available. 8. Avoid editing the PR repeatedly while distribution is pending. 9. Contact support for manual push verification. 10. Request a distribution audit if no outlets appear after 24 hours. Important Notes - Outlet reports populate asynchronously. - Initial reports may appear incomplete during the first several hours. ⚠️ Error 4: PR generated by AI has content I did not approve What's happening AI-generated PR content quality depends heavily on: - prompt specificity - company profile quality - and contextual business information. Vague inputs produce: - generic - inaccurate - or off-brand content. Steps to try 1. Always review AI-generated content before submission. 2. Edit any inaccurate sections manually. 3. Use Regenerate Section instead of regenerating the entire PR. 4. Add more detailed: - product information - announcement details - audience context - and brand positioning. 5. Avoid short prompts like: "write a press release." 6. Include: - what happened - why it matters - who it affects - and business context. 7. Update your Brand Vault information for better personalization. 8. Generate shorter sections first if results are inconsistent. 9. Save revisions before distribution. 10. Treat AI-generated PRs as first drafts, not final publications. Important Notes - More context produces dramatically better output quality. - Human review should always occur before distribution. ⚠️ Error 5: My company profile is not appearing in the distribution form dropdown What's happening Only fully saved company profiles appear in the PR distribution selector. Incomplete profiles may fail silently. Steps to try 1. Go to: Local → GBP Projects (GBP Projects) 2. Click Connect GBP Account if no profile exists. 3. Complete all required fields. 4. Save the profile completely. 5. Refresh the distribution form and reopen the company profile dropdown. 6. Wait several seconds for the list to refresh. 7. Confirm validation passed on every required field. 8. Contact support if the profile still does not appear after saving. Important Notes - Only fully validated company profiles surface in the selector. - Incomplete profiles may not display validation errors immediately. ⚠️ Error 6: Press release stuck in "Pending" or "Publishing" status What's happening A known visual glitch (referenced internally as AB-1006, marked resolved) can display a press release as "Pending" or "Publishing" even when the PR has actually been rejected by one or more distributors. In confirmed-rejection cases, HDC credits are refundable. Steps to try 1. Open the PR distribution status page and confirm the displayed status. 2. Allow 5–7 business days from submission for a publication link to appear. 3. If no publication link appears within 5–7 business days, contact support and reference the "stuck in Pending/Publishing" behavior (AB-1006). 4. Ask support to verify backend status — the PR may have been rejected by distributors even though the UI still shows it as publishing. 5. If rejection is confirmed, request a credit refund. 6. Avoid resubmitting the same PR while the status is still under investigation. Important Notes - AB-1006 is a known and resolved issue; edge cases may still require backend intervention by support. - HDC credits are refundable on confirmed rejection. Approximate credit cost per PR by tier: Street Insider 35, Digital Journal 30, News & Media 20, Local & National 15. - Do not wait several weeks before escalating — 5–7 business days with no publication link is the recommended threshold. ⚠️ Error 7: Distribution fails due to a temporary API outage or proxy authentication error (407) What's happening Transient backend failures can block distribution, including: - temporary API downtime - proxy authentication errors (e.g. 407 Auth failed) - and image-fetching failures from Brand Vault or Google Cloud Storage. These are server-side issues and are typically resolved without any customer action. Steps to try 1. Wait several minutes and retry submission once. 2. Check whether assets in Brand Vault load correctly in a separate tab. 3. Avoid repeatedly resubmitting while an outage is active — duplicate attempts will not bypass the failure. 4. Contact support if the error persists, and include the exact error text (for example, the 407 message or the failed image URL). Important Notes - These errors are usually resolved server-side; no customer action is required beyond a short wait and a single retry. - Persistent failures should be reported to support rather than retried indefinitely. ⚠️ Error 8: Logo or image upload fails with a "fetching image size" error What's happening Logo or image uploads can fail during PR submission with errors such as "fetching image size." When the error persists after resizing, reformatting, and trying a different browser, the root cause is usually a temporary backend or image-service outage — not a problem with the file itself. Steps to try 1. Confirm the image meets the documented format and size requirements (e.g. JPG or PNG, within the allowed dimensions). 2. Re-upload the image once. 3. Try uploading from a different supported browser. 4. If the error persists after these steps, stop retrying and contact support — repeated uploads will not resolve a backend outage. 5. Share the exact error text and the asset filename with support to speed up investigation. Important Notes - Persistent image errors are usually a sign of a temporary API outage rather than a user-side issue. - Once the file is confirmed to meet requirements, escalate to support instead of continuing to retry. ⚠️ Error 9: My press release was rejected by an outlet — what happens to my credits and notifications? What's happening When a distributor rejects a press release, the in-app status does not always visually update. A rejected PR can continue to display as "Pending" or "Publishing," which makes silent rejections difficult to identify from the UI alone. Steps to try 1. Wait 5–7 business days from submission for a publication link to appear. 2. If no link appears in that window, contact support and ask them to verify rejection status via the backend. 3. If support confirms a rejection, request a refund of the HDC credits consumed by the rejected distribution. 4. Review the rejection reason (when provided) before resubmitting, so the next draft can be adjusted accordingly. Important Notes - HDC credits are refundable on confirmed rejection. Approximate credit cost per PR by tier: Street Insider 35, Digital Journal 30, News & Media 20, Local & National 15. - A "Publishing" status alone is not proof of acceptance — backend verification by support is the reliable signal. - Escalate after 5–7 business days without a publication link rather than waiting several weeks.

📰 Fix Press Release Publishing with Hyperdrive Credits

🔍 Why You Can't Publish Your Press Release If you've uploaded a valid image and filled out all required fields but still can't publish your press release, the most common reason is a lack of Hyperdrive credits. Press release distribution in Search Atlas is powered by Hyperdrive, and each submission consumes a set number of credits from your account balance. This means the publishing button may remain inactive or return an error even when your content and image are correctly formatted — the system simply cannot proceed without enough credits available. 💳 What Are Hyperdrive Credits? Hyperdrive credits are the currency used to power premium content distribution features inside Search Atlas, including press release publishing. Credits are separate from your main subscription and must be purchased as needed or as part of a credit bundle. - Each press release submission deducts a fixed number of Hyperdrive credits from your balance. - Credits purchased as a one-time top-up do not expire and roll over until used, but Hyperdrive credits included in your plan (and any recurring monthly top-up) reset at each quota cycle and do not carry over. - Your current credit balance is always visible under Avatar → Billing → Plans & Top-ups (Billing). 🛒 How to Purchase Hyperdrive Credits 1. Log in to your Search Atlas account. 2. Locate the Hyperdrive Credits counter in the header area, near Open features menu. 3. Click Top Up next to Hyperdrive Credits under Avatar → Billing → Plans & Top-ups (Billing). 4. Select the credit package that fits your needs — larger bundles offer a lower cost per credit. 5. Complete the checkout using your saved payment method or enter new billing details. 6. Your credit balance will update immediately after the transaction is confirmed. 🚀 Publishing Your Press Release After Purchasing Credits 1. Return to the Press Releases section inside Search Atlas. 2. Open the draft you were working on, or create a new submission. 3. Confirm your image meets the required format and minimum dimensions shown on the upload screen. 4. Review all required fields — headline, body copy, contact details, and category. 5. Click Publish. The system will deduct the required credits and submit your press release for distribution. If the publish button is still unavailable after purchasing credits, try refreshing the page to allow your updated balance to load correctly. ✅ Quick Checklist Before Publishing - Credits available: Confirm your Hyperdrive balance covers the cost of one press release submission. - Image uploaded: Your image must meet the platform's format and size requirements (check the tooltip next to the upload field). - All required fields completed: Headline, body, contact information, and category must all be filled in. - Account in good standing: Ensure your Search Atlas subscription is active and your billing details are up to date. ❓ Still Seeing an Error? If you've purchased credits and your press release still won't publish, there may be an issue with your image file, a temporary platform error, or an account-level restriction. 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.

💳 PR Distribution Hyperdrive Credits Insufficient Balance Error

🔍 What This Error Actually Means When you try to submit a press release and see the message 'payment information needs to be updated', your first instinct may be to check your credit card or billing details. However, in most cases your payment method is perfectly fine. This error message is misleading. It is almost always triggered by an insufficient Hyperdrive credit balance — not a billing or payment issue. Your subscription can be fully active and your card completely valid, yet the error will still appear if you do not have enough Hyperdrive credits to cover the cost of your selected distribution. 📦 What Are Hyperdrive Credits? Hyperdrive credits are the in-platform currency used to submit press releases through the PR Distribution tool in Search Atlas. Each submission requires a minimum number of credits depending on the distribution tier and the number of outlets selected. - Credits are separate from your subscription billing. - You must have enough credits before you submit — the system does not automatically charge your card to top up your balance. - The minimum credit requirement varies by distribution package. For example, a standard submission may require 23 or more credits. ⚠️ Why the Error Message Is Confusing The platform surfaces a generic payment-related error when a submission cannot be processed due to insufficient credits. This is a known display issue. The underlying cause is a low or empty Hyperdrive credit balance, not a problem with your saved payment method. Steps like clearing your browser cache, re-entering your credit card, or contacting your bank will not resolve this error. The only fix is to ensure your Hyperdrive credit balance meets or exceeds the minimum required for your submission. ✅ How to Check Your Hyperdrive Credit Balance 1. Log in to your Search Atlas account. 2. Navigate to the PR Distribution tool from the left-hand menu. 3. Look for your Hyperdrive Credits balance, displayed in the top section of the PR Distribution dashboard. 4. Note your current balance and compare it to the credit requirement shown for your selected distribution package. 🛒 How to Add More Hyperdrive Credits 1. Click your Avatar → Billing → Plans & Top-ups (Billing), then click the Top Up button next to HyperDrive Credits. 2. Select the credit package that meets or exceeds the amount required for your press release submission. 3. Complete the purchase using your saved payment method. 4. Once the credits are added to your account, return to your press release draft and resubmit. Your credit balance updates immediately after a successful purchase, so you can resubmit your press release right away. 📋 Quick Troubleshooting Reference - Error appears even though card is valid: Check your Hyperdrive credit balance first — this is the most common cause. - Submission fails partway through: Your credit balance may have dropped below the minimum mid-session. Refresh the page and recheck your balance. - Not sure how many credits your submission requires: The credit cost is displayed on the submission review screen before you confirm. You can also check the pricing breakdown in the PR Distribution settings. - Credits were deducted but submission did not go through: Do not resubmit before contacting support, as you may be charged twice. Use the chat widget described below. 💡 Tips to Avoid This Error in the Future - Check your Hyperdrive credit balance before drafting a new press release, especially if you have submitted recently. - Keep a buffer of credits in your account if you submit press releases regularly. - Review the credit cost for each distribution tier before selecting your package so you are never caught short at the submission stage. 🙋 Still Need Help? If you have confirmed your credit balance is sufficient but the error persists, or if credits were deducted without a successful submission, please reach out. 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 PR Distribution Hyperdrive Credits Insufficient Error

What Is This Error? When you attempt to submit a press release through PR Distribution, you may see an error message such as "Payment information needs to be updated" or a notification that your credits are insufficient — even if your credit card is valid and your subscription is active. This error does not always mean your payment method has a problem. In many cases, it is related to your Hyperdrive credits balance or account configuration. Why Does This Happen? The error can appear for a variety of reasons related to your Hyperdrive credits or account status. Because the error message references payment information, it can be confusing — but the underlying cause is often a credits or account issue rather than a problem with your card. What to Do Because the exact cause and resolution of this error depends on your specific account configuration, our support team will need to review your account directly to identify what is blocking your submission and apply the correct fix. To help our team resolve this as quickly as possible, please have the following ready when you reach out: - The exact error message you are seeing (copy it word for word if possible). - The name of the press release project or draft you are trying to submit. - The date and approximate time the error occurred. - Any screenshots of the error, if available. 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. Additional Notes Credits are separate from subscription billing. The system does not automatically charge your card to top up your balance. The minimum credit requirement varies by distribution package (e.g. a standard submission may require 23+ credits). Steps like clearing cache or re-entering your card will NOT resolve this — only ensuring sufficient credit balance will.

📣 Check Your Press Release & Digital PR Distribution Status

📋 Overview When you submit a Press Release or Digital PR campaign through the Authority Building section of Search Atlas, you can track exactly where your content has been published — and see any refund details if a channel was unable to complete distribution. 🔍 How to Check Your Distribution Status 1. Log in to your Search Atlas account. 2. Navigate to the Authority Building section from the main left-hand menu. 3. Select Press Releases or Digital PR, depending on the campaign type you submitted. 4. Locate the campaign you want to review and click on it to open the detail view. 5. Scroll to the Distribution Status section to see a breakdown of each publication channel. 📡 Understanding Per-Channel Publication Status Each distribution channel in your campaign will display one of the following statuses: - Published — Your content was successfully distributed and is live on that channel. - Pending — Distribution is still in progress for this channel. Allow additional time for it to update. - Failed — The channel was unable to publish your content. See the refund section below for next steps. 💰 Refunds for Failed Channels If one or more distribution channels fail to publish your content, Search Atlas will issue a partial refund corresponding to the value of the failed channel(s). You can view the refund amount directly within the campaign's detail view under the Refund Summary section. Refunds are applied back to your Search Atlas account credits automatically — no additional action is required on your part. 💬 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 Press Release Project Selection via Brand Vault

Why Your Press Release Defaults to the Wrong Project The Press Release tool does not include a standalone project selector on its own page. Instead, it pulls your active project from Brand Vault. If you see an unexpected project name, it means that project is currently set as your active Brand Vault profile. Updating your active Brand Vault profile is the correct way to change which project appears in Press Release. This also applies to your Google Business Profile (GBP) project selection within Press Release. What You Will Need Before You Start - At least two projects already created inside Search Atlas - A Brand Vault profile set up for each project you want to use in Press Release - Sufficient access rights to your Search Atlas workspace How to Switch Your Active Project in Brand Vault 1. Log in to Search Atlas and navigate to Authority (Press Releases) in the left sidebar. 2. Review the list of your saved brand profiles. 3. Locate the profile that matches the project you want to use in Press Release. 4. Within Brand Vault, set that profile as your active profile using the options available in the Brand Vault interface. 5. Navigate to Authority (Press Releases) in the left sidebar. 6. Confirm the project name now reflects the correct project. If it does not update immediately, refresh your browser tab and check again. How to Set Up a Brand Vault Profile for a New Project If the project you need does not yet have a Brand Vault profile, you must create one before it can be selected in Press Release. This also applies if you want to associate a specific Google Business Profile (GBP) with a project in Press Release. 1. Go to Brand Vault and look for the option to create a new brand profile. 2. Select the correct project and fill in your brand details as prompted. 3. Save the new profile. 4. Follow the steps in the previous section to set this new profile as your active profile. Using Press Release After Switching Your Active Profile Once the correct Brand Vault profile is active, Press Release will reflect that project. If you manage multiple clients or projects, remember to return to Brand Vault and switch the active profile each time you want to generate a press release for a different project. Troubleshooting Common Issues - The project name still shows the old project after switching: Refresh your browser tab and navigate back to Authority (Press Releases). Browser cache can sometimes display stale data. - You cannot find the option to change the active profile or the Brand Vault setup is not behaving as expected: Our support team can review your account configuration and walk you through the correct steps for your workspace. 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 a Stuck Press Release and Request a Refund

🔍 Why Is My Press Release Stuck? Press releases can occasionally stall due to distribution partner delays, content review holds, or a technical issue during submission. If your press release has been pending for an extended period — including cases of several months — this requires immediate review by our support team. Common reasons a press release may not publish include: - The content was flagged during editorial review by the distribution partner - Missing or incomplete submission details (headline, contact info, or body content) - A technical error that prevented the order from being sent to the distributor - A temporary hold placed on the account ✅ Steps to Take Right Now 1. Check your order status — Log in to Search Atlas and locate your press release order. Confirm the current status shown on the order. 2. Gather your order details — Note the press release title, submission date, and any confirmation number or order ID. You will need these when contacting support. 3. Contact our support team immediately — A press release that has not published after an extended period qualifies for escalation. Our team can investigate the distribution status directly with our partner network. 💳 How to Request a Refund If your press release has not been published and a significant amount of time has passed, you may be eligible for a refund. Refunds are handled on a case-by-case basis by our support team. To request a refund: 1. Contact our support team using the chat widget described below. 2. Provide your order ID, the submission date, and confirm that the press release has not been published. 3. Our team will verify the order status and, if eligible, initiate the refund process on your behalf. ❌ How to Cancel Your Account If you would like to cancel your Search Atlas subscription in addition to requesting a refund, please contact our support team directly. A team member will assist you with processing both the refund and the account cancellation. When reaching out, please have the following ready: - Your account email address - The press release title and submission date - Confirmation that the press release was never published 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 Brand Vault Projects in Press Release

Overview When you open the Press Release section and try to select a project, Search Atlas pulls the available options from your Brand Vault and its connected Google Business Profile (GBP) locations. If your desired project does not appear in the dropdown — or the selector defaults to the wrong project — it almost always means the Brand Vault has not been fully configured or the GBP location has not yet been linked. This article explains the general relationship between Brand Vault setup and the Press Release GBP project selector, and tells you what to have ready when reaching out to support. How the GBP Project Selector Works The Press Release section does not draw from a general list of all your Search Atlas projects. Instead, it reads only from projects that have a Brand Vault entry with at least one linked GBP location. This means: - Creating a project in Search Atlas is not enough on its own. - You must also create a Brand Vault entry for that project. - The Brand Vault entry must have a GBP location associated with it. - Once the Brand Vault entry is properly configured, the project should become available in the Press Release selector. What to Check First Before escalating, verify the following in your account: - Confirm that a Brand Vault entry exists for the project you want to use in Press Release. - Confirm that a Google Business Profile location has been connected to that Brand Vault entry. - Try navigating away from the Press Release section and returning to it, or perform a hard browser refresh, to rule out a display issue. If you have checked all of the above and the project still does not appear, the issue will need to be investigated by our support team. When Escalating to Support Because Brand Vault configuration and GBP linking involve account-specific settings, our team may need to review your setup directly. To help us resolve this as quickly as possible, please have the following ready: - The exact name of the project or brand that is not appearing in the Press Release selector. - Whether a Brand Vault entry exists for that brand and whether a GBP location has been added to it. - Any error messages you see when attempting to link a GBP location or access the selector. - The approximate time you first noticed the issue. 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 Insufficient Credits When Publishing Press Releases

🔍 Why This Error Appears Seeing an Insufficient Credits error when you have credits available can be confusing. This error does not always mean your account is out of credits overall — it may mean that the credits available on your account are not the type required for press release publishing. 📊 Understanding Credit Types Search Atlas may use different credit types for different content and features. Having credits in your account does not automatically mean those credits are the type required for press release publishing, so it is worth checking which credit type your account holds -- and how it applies to press releases -- before attempting to publish. 🛠️ What to Do When You See This Error Because the source of this error varies by account, the most reliable path to resolution is to reach out via the support chat widget. When you do, please have the following ready so the team can investigate and resolve your issue quickly: - Your account name or registered email address. - The exact error message you are seeing when you attempt to publish. - A description of your current plan and any recent changes (e.g., upgrades, renewals, or plan switches). - The number and type of credits shown in your account dashboard at the time of the error. - Any screenshots of the error and your credit balance if possible. A member of the support team will be able to confirm whether your account has the correct credit type assigned, and take any backend action needed to resolve the issue. 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 the Digital PR Outreach Schedule Configuration Error

🔍 What This Error Means The 'Please configure outreach schedule first!' error appears in Digital PR when you attempt to launch or send a campaign before the outreach schedule has been fully set up. This is not just about connecting an email account — the schedule itself must be created and saved as a separate step. Both requirements must be completed before a campaign can run. ✅ Step 1 — Confirm Your Email Account Is Connected Before configuring a schedule, verify that an email account is linked to your workspace: 1. Go to Left sidebar → Authority → Campaigns. 2. Open or create a campaign, then look for the sending email address field. 3. If no email is connected, navigate to your account settings and connect a valid sending email address. 4. Return to Campaigns and confirm the email address now appears as an option. If your email is already connected and the error persists, do not stop here — proceed to Step 2. A connected email alone is not enough to clear this error. 📅 Step 2 — Create and Save an Outreach Schedule This is the most commonly missed step. Even with a connected email, you must configure a dedicated outreach schedule: 1. Go to Left sidebar → Authority → Campaigns. 2. Open the campaign that is triggering the error. 3. Locate the Schedule or Outreach Schedule section within the campaign settings. 4. Set your preferred sending days and time windows. 5. Click Save to confirm the schedule. Do not navigate away before saving. 6. Return to the campaign overview and attempt to launch or send again. The error should clear once a schedule has been saved against the campaign. If the error still appears after completing both steps, continue to the decision tree below. 🔁 Persistent Error — Decision Tree Use the following checks in order if the error has not resolved after Steps 1 and 2: - Did you save the schedule before leaving the settings page? Navigating away without clicking Save discards the schedule. Repeat Step 2 and confirm the save action completes before moving on. - Is the schedule attached to the correct campaign? Schedules are campaign-specific. If you have multiple campaigns, confirm the schedule was saved inside the campaign you are trying to launch, not a different one. - Did you create the campaign in draft mode? Some draft campaigns require you to fully publish or activate the campaign record before a schedule can be applied. Look for an Activate or Publish button and complete that step first, then re-add the schedule. - Has your connected email account been disconnected since you last used it? Token expiry or password changes can silently disconnect an email. Go to Left sidebar → Authority → Campaigns, check the sending email field, and reconnect if needed. - Are you seeing the error on a cloned or duplicated campaign? Duplicated campaigns do not carry over schedule settings. You must configure a new schedule for each copy. 📥 Check Your Inbox and Sent Items After a successful campaign launch, you can monitor activity in two places: - Left sidebar → Authority → Inbox — incoming replies from your outreach. - Left sidebar → Authority → Sent — confirmation that emails were dispatched by the schedule. If the Sent folder remains empty after your scheduled send window has passed, the schedule may not have saved correctly. Repeat Step 2 and verify the send window covers the current time and day. ⚠️ When to Contact Support If you have completed all steps above and the error still appears, or if the Sent folder remains empty after two full schedule cycles, this may indicate a backend configuration issue that requires investigation. 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 Press Release Hyperdrive Credit Errors

🔍 Overview When you attempt to publish a press release using Hyperdrive, Search Atlas checks your available credit balance in real time. If the system detects that your balance is insufficient — even if you believe you have enough credits — a publication error will appear and the press release will not be submitted. This article walks you through how to verify your balance and resolve the issue. 📊 Step 1: Check Your Hyperdrive Credit Balance Before troubleshooting the error, confirm your actual available balance: 1. Log in to your Search Atlas account. 2. Navigate to the top-right Avatar Menu (👤) → Billing (Billing) page. 3. Locate the Hyperdrive Credits panel and note your current balance. 4. Compare the displayed balance against the credit cost shown on the press release publication screen. If your balance is lower than the required amount, you will need to purchase additional Hyperdrive credits before publishing. ⚙️ Step 2: Refresh Your Session Occasionally, a cached session may display an outdated credit balance, causing a mismatch between what you see and what the system reads. To rule this out: 1. Save any draft content you are working on. 2. Fully log out of Search Atlas. 3. Clear your browser cache and cookies, or open Search Atlas in a private/incognito window. 4. Log back in and navigate back to your press release. 5. Check the credit balance again and attempt to publish. 🛠️ Step 3: Verify Credit Type and Plan Eligibility Not all credits are interchangeable inside Search Atlas. Keep the following in mind: - Hyperdrive Credits are specifically required for press release distribution. General platform credits or other credit types cannot substitute for them. - Confirm that your current subscription plan includes access to Hyperdrive press release publishing. - If your credits were recently purchased or added by a team administrator, allow a few minutes for the balance to sync, then refresh your session as described in Step 2. 💡 Step 4: Review Recent Credit Usage It is possible that recent activity consumed credits you were not aware of. To check: 1. Go to your Billing or Usage History section. 2. Review recent Hyperdrive transactions to see if credits were used for other press releases or services. 3. If you notice any unrecognised charges or unexpected deductions, make a note of the dates and amounts before contacting support. 🚀 Step 5: Attempt Publication Again Once you have confirmed your balance is sufficient and your session is refreshed, retry publishing your press release: 1. Open the press release you want to publish. 2. Review all required fields to ensure the submission is complete — incomplete submissions can sometimes trigger misleading error messages. 3. Click Publish and monitor the confirmation screen. If the error persists after completing all steps above, do not restart repeatedly, as this will not resolve an underlying balance or account issue. ⚠️ Common Reasons the Error Appears - Your Hyperdrive credit balance is genuinely below the required amount for the selected distribution tier. - A recent purchase has not yet been reflected due to a brief sync delay. - Your session is displaying a stale balance from before a credit deduction. - Your subscription plan does not include Hyperdrive press release access. - A temporary platform issue is affecting credit reads — in this case, waiting a few minutes and retrying often resolves it. 🙋 Still Seeing the Error? If you have followed all the steps above and the publication error continues, our support team can investigate your account balance, recent transactions, and any platform-side issues directly. 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 Press Release Insufficient Credits Error

🔍 What This Error Means Seeing an insufficient credits error while trying to publish a press release — even when your credit balance looks healthy — usually points to a quota type mismatch, not a simple lack of credits. Press release publishing draws from your Hyperdrive Credits balance, which is a different pool from your general AI content credits. Having a healthy general AI-credit balance does not automatically mean you have enough Hyperdrive Credits available for press release publishing - the two are tracked separately. 🗂️ Understanding Credit Pools Your Search Atlas account manages more than one credit pool. The two most relevant here are: - General AI Credits: Used for AI writing, content generation, and similar tools. - Hyperdrive Credits: Used for press release publishing and other high-volume distribution actions. When you attempt to publish a press release, the system checks only your press release credit balance. If your Hyperdrive Credits balance is at zero or below the required threshold, you will see the insufficient credits error - regardless of how many general AI credits you hold. ✅ How to Check Your Press Release Credit Balance 1. Log in to your Search Atlas account. 2. Click your Avatar Menu (👤) or account name in the top-right corner. 3. Navigate to Billing or Subscription & Credits. 4. Look for the Hyperdrive Credits line item specifically - do not rely on your general AI credit total shown on the dashboard overview. 5. Confirm whether your press release credit balance is sufficient for a new publication. 🛠️ Steps to Resolve the Error 1. Verify the correct credit pool: Confirm your press release credits balance as described above. Do not assume the general credit counter reflects press release availability. 2. Check your current plan: Some subscription tiers include a limited monthly allocation of press release credits. If you have used your allocation for the billing cycle, the balance resets on your renewal date. 3. Review your billing cycle reset date: If your press release credits are exhausted, note when your next billing cycle begins so your quota will automatically refresh. 4. Consider a credit top-up or plan upgrade: If you need to publish before the reset date, you may be able to purchase additional press release credits or upgrade your plan to receive a higher monthly allocation. Check the Billing section for available options. 5. Retry publishing after confirming credits are available: Only retry the publish action once you have confirmed the press release credit balance is sufficient. Retrying before resolving the underlying quota issue will produce the same error. ⚠️ Common Mistakes to Avoid - Assuming general AI credits = Hyperdrive Credits. Always check your Hyperdrive Credits balance specifically, not your general AI credit total. - Retrying immediately without checking balances. The error will persist until the correct credit pool has sufficient funds. - Confusing a billing cycle reset with an account issue. If your quota resets monthly, an empty press release credit pool is expected behaviour near the end of a cycle — not a platform bug. 🙋 When to Contact Support Reach out to the support team if any of the following apply after following the steps above: - Your press release credit balance shows available credits but the error still appears. - Credits were deducted without a successful publish completing. - Your credit balance does not match what your plan states you should receive. - You are unable to locate the press release credit line in your billing dashboard. 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 WordPress CMS Sync & PR Distribution Errors

🔍 Overview Some customers have reported two related issues when working with OTTO: a false error stating that no WordPress site was detected during CMS sync, and a PR Distribution job that stalls at 50% progress. This article explains why these issues occur and how to resolve them. ⚠️ What You May Be Experiencing - OTTO's CMS sync fails with a message like "No WordPress site detected" even though your WordPress site is connected. - Your PR Distribution job is stuck at 50% and does not complete. - Your WordPress Connector appears disconnected in the dashboard after a sync attempt that seemed successful. 🛠️ Why This Happens These issues are caused by a known bug in OTTO's CMS sync process. The system incorrectly triggers a WordPress detection check during sync, which can return a false negative — meaning it reports no WordPress site even when one is properly connected. This false error can interrupt the sync task and cause downstream jobs, such as PR Distribution, to stall mid-progress. Our engineering team has identified the root cause and a fix is currently in release. Once deployed, the false detection error will be resolved and sync tasks will complete reliably. ✅ Steps to Try Right Now While the fix is being rolled out, the following steps resolve the issue for most customers: 1. Reconnect your WordPress site. Go to Settings → CMS Connectors (or Settings → Integrations) and disconnect your site, then reconnect it using your credentials. 2. Re-run the CMS sync. After reconnecting, trigger a new CMS sync from the OTTO dashboard. Wait for the sync to complete fully before proceeding. 3. Restart the PR Distribution job. Once the sync completes successfully, cancel the stuck PR Distribution job and create a new one. It should now progress past 50% without issue. 4. Verify your connector status. After the sync, confirm that your WordPress Connector shows as Connected in the Connectors panel. If it still shows as disconnected, repeat step 1. 📋 Additional Things to Check - Make sure your WordPress site is live and accessible — OTTO cannot connect to sites that are in maintenance mode or behind a login wall. - Confirm that the Search Atlas WordPress plugin is installed, activated, and up to date on your site. - Check that your WordPress credentials (username and application password) have not expired or been changed recently. - If you are publishing content, note that articles with a workflow status of Needs Review will not be included in published content lists — only fully approved content is synced. 🚀 What Our Team Is Doing Our engineering team is actively working on this. Here is the current status of related fixes: - False WordPress detection error during CMS sync — fix is in release and will be deployed shortly. - CMS sync failures now surface proper error messages — improved error handling is in progress so you will see clear, actionable feedback if a sync fails in the future. - WordPress Connector disconnecting after sync — this bug has been resolved in a recent update. You do not need to take any action to receive these updates — they will be applied automatically to your account. 💬 Still Need Help? If you have followed the steps above and are still experiencing issues, 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.

🖼️ Brand Vault Logo Converting to WEBP Blocking Press Release Distribution

🔍 What Is Happening When you upload a PNG or JPG logo to the Brand Vault, the platform may automatically store it as a WEBP file internally. Because press release distribution does not support the WEBP format, any press release that references that logo will fail to distribute and display an error indicating a WEBP image was detected — even though you originally uploaded a supported file type. This is a known platform issue (tracked internally as AB-1048). Engineering has already shipped fixes to prevent WEBP blocking during press release distribution, and additional improvements are in progress. However, if you are currently seeing this error, the steps below can help you clear it right now. ⚠️ Symptoms - Your press release fails to distribute with a message about a WEBP image being present. - You re-upload a PNG or JPG logo in Brand Vault, but the error persists. - The logo appears to change format after uploading, even though your original file is a supported type. 🛠️ How to Fix It 1. Go to your Brand Vault. From the header, click the apps-grid icon → More Features → Brand Vault. 2. Locate the logo that is causing the issue. Find the logo associated with the brand profile linked to your press release. 3. Remove the existing logo. Delete or replace the current logo stored in the Brand Vault — do not skip this step, as simply re-uploading on top of the existing file may not resolve the conversion issue. 4. Re-upload a clean PNG or JPG file. Use a freshly exported PNG or JPG version of your logo. Make sure the file has not been previously processed or saved in WEBP format by any other tool before uploading. 5. Save your Brand Vault changes. Confirm the update is saved within the Brand Vault before returning to your press release. 6. Return to your press release and attempt distribution again. After updating the logo directly in the Brand Vault, the WEBP-related error should clear and distribution should proceed normally. 💡 Additional Tips - Always use a PNG or JPG file exported directly from your design tool (such as Adobe Illustrator, Figma, or Canva) rather than a file downloaded from a website, which may already be in WEBP format. - If you have multiple brand profiles in your Brand Vault, check that the press release is linked to the profile whose logo you just updated. - Once the logo is updated in Brand Vault, you do not need to re-create the press release — simply retry distribution from the existing draft. 📋 Platform Improvements Already in Place Search Atlas engineering has resolved the error that blocked press release distribution for PNG and JPG images stored as WEBP (ticket AB-1048). If you continue to experience this issue after following the steps above, please reach out to our support team for further assistance.

Get Credits Refunded for a Failed Press Release

🧐 What This Article Covers If you paid Hyperdrive credits to publish a press release and the publication failed, you are entitled to have those credits restored to your account. This article explains what to expect and how to request a refund quickly. 📋 Why a Publication Can Fail Press release distribution involves multiple third-party channels. Occasionally, a publication may not go through successfully on one or more of those channels. When that happens, the credits used for the failed publication should not be lost. - A channel may reject the submission due to formatting or eligibility requirements. - A local distribution option may not complete if the selected region could not be served. - Partial failures can occur where some channels publish successfully and others do not. Important: When a publication fails, is unpublished, or distributions are missing or their links expire, the Hyperdrive credits for the affected part are refunded to your account automatically and you will receive a refund notification. External submissions are excluded from this automatic refund. 🔍 How to Check Your Publication Status Before reaching out, confirm that your publication actually failed by reviewing its status in the platform. 1. Navigate to the press release section of the platform where your distributions are listed. 2. Locate the press release in question and review its publication status. 3. Check the status for each channel. A failed or incomplete status on any channel confirms that the distribution did not go through for that channel. Note the number of credits you spent and which channels failed, as this information will help the support team process your refund faster. 💬 How to Request Your Credit Refund Credit refunds for failed publications are issued automatically, but if you believe a refund was missed or you need help with an external submission, the support team can assist: 1. 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. 2. Share the name of the press release and confirm which publication channels failed. 3. The agent will verify the failure on their end and restore the appropriate number of Hyperdrive credits to your account. In a confirmed case, an agent was able to restore 55 Hyperdrive credits after verifying a failed publication, with the credits available immediately after the reset. ✅ What to Expect After the Refund - The restored credits will be available in your account right away. - You can use the refunded credits to re-publish the press release or apply them to a new distribution. - Partial refunds are also supported — if only some channels failed, only the credits for those channels will be restored. 🛠️ Still Need 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 PR Distribution Blocked by Blog Headline Error

🔍 What This Issue Looks Like You fill in the Blog Headline and Blog Summary fields for your press release, the dashboard shows both fields as complete, but when you attempt to publish, the distribution is blocked. The underlying API reads those fields as null, and you receive an error similar to: "The blog headline field is required." Your press release stays unpublished and your HDC quota is not consumed. 📋 What Caused This This was a confirmed platform bug where the PR Distribution system did not correctly pass filled-in blog metadata to the publishing API, causing it to treat populated fields as empty. An engineering fix has been deployed to production, so new press releases should publish without this error. Failed press releases also do not consume your HDC quota, so you will not lose credits for a blocked attempt. ✅ Steps to Resolve 1. Navigate to the PR Distribution section of the platform. 2. Locate the press release that failed to publish. If it shows a failed or blocked status, do not attempt to re-submit it immediately — first confirm the steps below. 3. Open the press release and verify that the Blog Headline and Blog Summary fields contain your intended content. Even if they appeared filled before, clear each field and re-enter the content to ensure the platform registers the values correctly after the fix. 4. Save your changes before attempting to publish again. 5. Proceed to publish the press release. With the engineering fix now live in production, the API should correctly receive the blog metadata and allow distribution to proceed. 6. If the press release still shows a blocked or failed status after re-entering your content and saving, do not re-submit multiple times. Contact support using the method described below so a specialist can review your specific press release. 💡 About Your HDC Quota Press releases that fail due to this error do not consume your HDC quota. A failed distribution is not counted against your credits. If you believe credits were incorrectly deducted as a result of this bug, note the affected press release details and contact support — the team can review and apply a correction where appropriate. ⚠️ If the Problem Persists This bug has been patched, but if you continue to see the same error after following the steps above, it is important to escalate promptly rather than retrying repeatedly. Provide support with the name of your press release and the approximate time you attempted to publish so the team can investigate your account directly. 💬 Get 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 Press Release Address Display Errors

🔍 Overview When creating a press release in Search Atlas, some customers notice that address information does not display as expected on the final published version. The most common symptom is the city name appearing multiple times in the address block. This type of issue may require backend correction by the Search Atlas team. ⚠️ Common Address Display Issues - City name duplicated: The city appears more than once in the address field (e.g., "Austin, Austin, TX 78701"). - Incorrect field mapping: Address components such as city, state, or ZIP code are placed in the wrong fields. - Address not displaying correctly on the published version of the press release. These issues may occur when the press release form auto-fills your business information and one or more fields contain duplicated or misformatted data. 🛠️ What You Can Try 1. Open the press release editor and navigate to the press release you want to fix. 2. Review each address field individually — street address, city, state, and ZIP code — and check for duplicated or incorrect values. 3. Clear any duplicated values. If the city field contains the city name more than once (e.g., "Austin, Austin"), delete the entire contents of that field and retype the correct value. 4. Save and republish the press release, then confirm the address appears correctly on the published version. If the address still does not display correctly after editing, this may require a backend correction by the Search Atlas support team. 📋 What to Have Ready When Escalating If you need to contact support about this issue, please have the following information ready so the team can investigate and resolve it quickly: - The name or URL of the affected press release - The exact address that should appear (street, city, state, ZIP) - A description of what is currently displayed incorrectly (e.g., city name appears twice) - A screenshot of the incorrect address display, if possible 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 Google Business Profile Map in Press Releases

What Is Happening When you add a Google Business Profile map embed to a press release, the map may display a generic coordinate pin instead of your verified Google Business Profile listing. This is a known bug that our team is actively investigating. If you are experiencing this issue, please follow the escalation steps below so our team can look into your specific case. What to Have Ready Before Escalating To help our team resolve this as quickly as possible, please gather the following information before reaching out: - Your project name — the exact name of the project where the map embed is not displaying correctly. - The press release where the issue occurs — include the title or URL of the affected press release. - A description of what you see — for example, whether the map shows a generic pin, no map at all, or something else unexpected. - The embed code you are using — copy and paste the full iframe or embed snippet so our team can inspect it. - When the issue started — note the approximate date and time you first noticed the problem. Having these details ready will allow our team to investigate your account and identify the root cause without delay. 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.

📰 Automatic Refunds for Failed Press Releases

📋 Overview When you submit a press release through Search Atlas, it is distributed across multiple partner channels. Occasionally, a specific channel may fail to publish your release. In these cases, Search Atlas automatically issues a partial refund for any channel that did not successfully pick up your content — no manual request needed. 🔄 How the Automatic Refund Works Our system monitors the publication status of every press release across all distribution channels. If a channel fails to publish your release, a partial refund corresponding to that channel's cost is calculated and applied automatically. You do not need to submit a support ticket or fill out any form to receive your refund. 💡 Important Things to Know - Refunds are partial — they apply only to the specific channel(s) that failed, not the entire press release submission. - Refund amounts vary depending on which channel failed, as each distribution partner carries a different weight in the overall cost. - Successfully published channels are not refunded, even if other channels in the same submission failed. 🛠️ Troubleshooting and Support If you believe a refund for a failed channel has not been applied, or if you have questions about the status of your press release distribution, please have the following ready when you reach out: your press release title, the submission date, and any details about the channel(s) you believe failed to publish. 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.

Press Release 'Headline Taken' Error Fix

What This Article Covers Some users encountered an issue where attempting to publish a press release returned a 'headline already taken' validation error, even when the headline was unique and had not been used before. This article explains what is known about the problem and how to get it resolved. What Caused the Issue This was a confirmed bug in the press release publishing process. The platform's validation logic was incorrectly flagging valid, unique headlines as duplicates when they were not. The error did not reflect a real conflict — it was a false positive produced by a fault in the backend validation check. What To Do Because this issue is caused by a backend validation bug, it cannot be resolved through self-service steps alone. To get your press release published, please contact the Search Atlas support team directly. When you reach out, have the following ready so the team can locate and correct your record as quickly as possible: - The URL of the affected press release - The exact headline text you are trying to use Do not repeatedly attempt to publish while waiting for a response — this will not resolve the underlying issue. Once the support team confirms the fix has been applied, return to your press release and attempt to publish again. The 'headline already taken' error should no longer appear. If you need help, please contact our support team via the chat icon in your Search Atlas dashboard.

🚨 Digital PR Campaigns Stuck in FAILURE Status

Overview Some Digital PR outreach campaigns can become stuck in a FAILURE status during contact processing. When this happens, you may see 0 contacts extracted and no processing activity — even after waiting an extended period. This article explains what causes this issue and what steps to take if you encounter it. What Causes This Issue A platform-level issue has been identified where outreach campaigns that reach a FAILURE status may not be automatically retried by the system. As a result, contact discovery never re-executes and the campaign remains stuck with no contacts processed and no further progress. This is not caused by anything in your account settings or campaign configuration. It is a backend processing issue that requires intervention to resolve. How to Identify This Problem Your campaign is likely affected if you observe all of the following: - One or more outreach campaigns display a FAILURE or failed processing status - The contact discovery stage shows 0 contacts extracted - The campaign has not progressed or updated over a significant period of time - Refreshing or waiting does not change the status You can review your campaign statuses by navigating to your Digital PR outreach campaigns section of the platform. What to Do If Your Campaigns Are Stuck If your campaigns show a FAILURE status and contacts are not being discovered or processed, follow these steps to get your campaigns re-triggered as quickly as possible: 1. Navigate to your Digital PR outreach campaigns in the platform and identify which campaigns are showing a FAILURE status. 2. Note the name or ID of each affected campaign, how long it has been stuck, and when each campaign was originally created. 3. Note the total number of campaigns affected in your account. 4. Take a screenshot of the FAILURE status for each affected campaign if possible. 5. Try duplicating the affected campaign and launching the duplicate as a new campaign. In some cases, creating a fresh copy allows the contact discovery pipeline to run successfully and avoids the stuck state entirely. 6. If duplicating and relaunching the campaign does not resolve the issue, contact our support team with the information gathered above so they can manually re-trigger contact discovery for your specific campaigns. What Happens After You Report It Once our team receives your report, they will escalate to engineering to re-trigger the contact discovery pipeline for your affected campaigns. You should see your campaigns move out of FAILURE status and begin processing contacts after the re-trigger is applied. Our team will follow up to confirm when the fix has been applied to your account. If you are unsure whether your campaigns are affected or need help identifying the issue, please don't hesitate to reach out — use the chat button below to contact our support team and we will investigate on your behalf.

Digital PR Outreach Blocked Despite Available Credits

Overview Some accounts have a configuration setting that prevents the Digital PR email connection feature from being activated. When this setting is missing, your campaign will appear as Paused and any attempt to start outreach will fail with an error — even if you have sufficient credits available. This is a backend account configuration issue, not a problem with your campaign setup or credit balance. Symptoms - Your Digital PR campaign shows a Paused status. - Clicking the option to start outreach does nothing or returns an error. - You have enough credits but the feature remains inaccessible. - Reconnecting your email account or refreshing the page does not resolve the issue. How to Confirm This Is Your Issue 1. Navigate to your Digital PR campaigns and open the affected campaign. 2. Confirm the campaign status shows Paused and that starting outreach produces no result or triggers an error. 3. Verify your credit balance is sufficient for outreach by checking your account quota information. 4. If both conditions are true — campaign is paused and credits are available — the issue is very likely a disabled account-level feature flag that only our support team can escalate to an admin to enable. How to Fix It This issue requires a Search Atlas admin to enable the Digital PR email connection feature flag for your specific account. Because this is a backend configuration change, you will need to contact our support team to get it resolved. Here is how to do that as efficiently as possible: 1. Open the chat widget in the bottom-right corner of the platform and start a conversation with our support team. 2. In your message, include: - The name of the affected campaign. - Your account email address. - Confirmation that your credits are available but outreach cannot be started. - A screenshot of the error or Paused status if possible — this helps our team locate your account and escalate faster. 3. Our support team will identify the disabled feature flag on your account and escalate to an admin to enable the Digital PR email connection on the backend. 4. Once our team confirms the fix has been applied, return to your Digital PR campaign and attempt to start outreach again. 5. If outreach still does not start after the flag has been enabled, reply in the same chat thread so our team can verify the change took effect on your account. Why Self-Service Is Not Possible for This Issue The feature flag that controls Digital PR email connection access is set at the backend account level and cannot be toggled from within the platform interface. There are no settings in your account dashboard that will resolve this — the change must be made by a Search Atlas admin. Contacting support is the only path to resolution, and our team is equipped to escalate and apply the fix on your behalf.

📰 Press Release Distribution Failures: How Refunded Credits and Republication Work

📋 Overview When you distribute a press release through Search Atlas, your content is pushed to a network of media channels and syndication partners. Occasionally, one or more of these channels may fail to publish due to issues on the receiving network's side, formatting conflicts, or temporary outages. This article explains how Search Atlas handles those failures, how credits are refunded, and how to republish the affected channels without being charged twice. Refunds for press release distribution are issued in Hyper Drive Credits (HDC). ⚠️ Why PR Channels Sometimes Fail A press release distribution can partially fail even when most channels succeed. Common reasons include: - A downstream media partner is temporarily unavailable or rejects the submission. - The release contains formatting, character, or link issues that a specific channel will not accept. - A network applies its own editorial review and declines the content. - Temporary connectivity or timeout errors between systems. When this happens, the channels that published successfully remain live. Only the failed channels need attention. A channel is treated as a confirmed failure when it has received no published media URLs after the distribution report is finalized (the report-available state). At that point the channel will not receive URLs later, so it is marked as failed and refunded automatically. 💰 How Refunds for Failed Channels Work You are never charged for distribution that does not complete. When a channel fails to publish, Search Atlas automatically credits your account for the portion that did not go through. 1. The system detects which channels failed during or after distribution. 2. The HDC tied to those specific failed channels are returned to your account balance. For a partial failure, the refund is proportional to the channels that failed, so you keep full value for the channels that did publish. 3. You can view the refunded credits in your account's billing or credits section. This means the cost of a partial failure is reversed, and you keep full value for any channels that did publish successfully. 🔎 Where to See Per-Channel Status and Refunds Each channel reflects its own state rather than a single shared status for the whole release. On the Publication Status modal (and the View Status table), every channel shows one of the following statuses: - Published – the channel published successfully. - Publishing – distribution is still in progress for that channel. - Publish failed – the channel did not publish; the refunded amount is shown next to it (for example, "20 HDC refunded"). - Publish stuck – the channel is in a stalled state and is being resolved. For rejected or failed channels, the View Status table includes a Refunded column so you can confirm the refunded amount inline without leaving the screen. 🔁 How to Republish Failed Channels Without Duplicate Charges The most common concern is being charged twice: once for the original attempt and again for the republication. Because failed channels are refunded before republication, this does not happen. You only pay for channels that actually publish. 🛠️ Option 1: Republish Yourself 1. Open the press release report for the affected distribution. 2. Review the channel status list to confirm which channels are marked as Publish failed. 3. Confirm that the HDC for those failed channels have been returned to your account balance (and shown in the Refunded column). 4. Use the republish option to resubmit only the failed channels. 5. The republication consumes the refunded credits, so your net cost stays the same as a single successful distribution. Note: republishing press releases that are in a failed (Publish Failed) state now works as expected. A previously reported issue, where republishing a failed press release was silently ignored, the status did not change, and no quota was consumed, has been fixed. 🤝 Option 2: Have the Search Atlas Team Handle It Yes, our team can manage republication from the backend for you. This is useful if a failure is recurring, if you are unsure which channels need resubmission, or if you simply prefer us to handle it. 1. Contact support and reference the specific press release or order. 2. Our team verifies the failed channels and confirms the refunded credits. 3. We republish the affected channels on your behalf, using the refunded credits. 4. We confirm completion and share the updated channel status with you. In both options, the refund-then-republish sequence ensures you are not double-charged. ✅ How to Confirm You Were Not Charged Twice To verify everything balanced correctly, check the following after republication: - Credits balance: The refunded HDC should appear, then be applied to the republished channels. - Channel status: Previously failed channels should now show as published. - Order history: The net credits used should match a single successful distribution, not two full charges. - Credit cost consistency: The per-channel credit cost you see should match the actual cost charged. If a channel's displayed cost looks inconsistent, contact support so we can verify the correct amount was refunded. If any of these do not line up, contact support with your order details and we will reconcile it. 💡 Tips to Reduce Future Failures - Avoid unusual characters, broken links, or overly promotional language that some networks reject. - Keep formatting clean and within recommended length guidelines. - Wait for the full distribution report before assuming a release failed, as some channels publish on a delay. 📞 When to Contact Support Reach out to our team if: - Refunded credits do not appear after a channel failure. - The same channels fail repeatedly after republishing. - You would prefer Search Atlas to handle republication for you. - You see charges that do not match the channels actually published. Include your press release name or order ID so we can resolve the issue quickly.

✍️ Content Rewriting & Press Release Troubleshooting

✍️ Content Rewriting & Press Release Troubleshooting This article covers: AI rewriting generation, rewrite queue delays, semantic drift, plagiarism similarity, brand voice alignment, keyword preservation, language configuration, rewrite processing failures, and Press Release publication issues (including typos, retractions, and credit refunds). Content Rewriting is designed to: paraphrase content, improve readability, create alternate versions, reduce duplication, and adapt tone or structure while preserving the original meaning as closely as possible. Because rewriting uses large language models: outputs vary between generations, semantic interpretation can shift, and rewrite quality depends heavily on: source clarity, rewrite intensity, formatting, and content complexity. ⚠️ Error 1: Rewrite button is not responding after clicking What's happening Rewrite requests are processed through a background AI queue. During peak traffic periods: requests may remain queued temporarily, processing workers may delay execution, and the UI may appear unresponsive while the task initializes. Steps to try - Wait at least 10–15 seconds after clicking Rewrite. - Avoid clicking the button repeatedly during queue processing. - Refresh the page if nothing happens after 30 seconds. - Rewrite smaller sections instead of entire articles. - Keep rewrites under 500–800 words for fastest processing. - Close unnecessary browser tabs to reduce memory load. - Try Chrome if another browser is producing UI delays. - Disable browser extensions that interfere with scripts. - Retry during off-peak hours if queues remain slow. - Contact support if rewrite tasks never start across multiple projects. Important Notes - Queue delay does not necessarily indicate failure. - Large rewrites process significantly slower than small sections. ⚠️ Error 2: Rewritten content has a completely different meaning from the original What's happening Semantic drift occurs when: source content is ambiguous, technical language lacks context, or rewrite intensity is too aggressive. The AI may reinterpret the meaning instead of paraphrasing it closely. Steps to try - Set Rewriting Intensity to: Light or Moderate. - Rewrite one section at a time instead of the full article. - Simplify unclear or highly technical sentences before rewriting. - Use shorter paragraphs for more stable rewrites. - Compare outputs using Compare View after generation. - Restore important terminology manually if needed. - Avoid stacking multiple rewrites on the same text. - Add context before rewriting technical sections. - Use Heavy Rewrite only for major structural changes. - Manually QA all rewritten factual statements before publishing. Important Notes - Smaller rewrite chunks preserve meaning more accurately. - Aggressive paraphrasing increases semantic drift risk. ⚠️ Error 3: Rewritten content does not match my brand voice What's happening Without Brand Vault integration: rewriting defaults to generic language patterns, neutral tone, and generalized phrasing. Brand voice guidance only applies when: a Brand Vault is selected and the rewrite session starts with that vault enabled. Steps to try - Select the correct Brand Vault before starting the rewrite session. - Verify the Brand Vault contains tone, style, and terminology guidelines. - Re-run the rewrite after enabling the vault if it was missed initially. - Manually adjust phrasing post-rewrite if brand alignment is critical. ⚠️ Error 4: Press Release contains a typo or incorrect information (e.g., wrong location, name, or detail) What's happening Press Releases distributed through Search Atlas follow a one-way publication workflow. Once a PR moves out of draft and is submitted to the distribution network: - Drafts can be freely edited before submission. - PRs in Publishing status are mid-distribution and cannot be edited by the customer directly, but support can retract them internally if distribution has not yet completed. - Published PRs cannot be edited, recalled, or modified post-publication, because syndication partners and news outlets have already received the content. Common example: a customer publishes a PR listing a location as "Redmond, OR" instead of "Redmond, WA" and needs to correct it. Steps to try - Before submission: proofread the PR carefully in draft mode. Verify location, names, dates, URLs, and contact details. - If the PR is stuck in 'Publishing' status: contact support immediately. Support can retract PRs internally before distribution finalizes so you can correct and republish. - If the PR is already 'Published': publication cannot be reversed. You will need to issue a corrected/updated PR as a new submission. The original cannot be retracted from syndication partners. - Provide support with the PR ID(s) and a clear description of the typo or required correction. Credit (HDC) refund policy - When support retracts PRs stuck in 'Publishing' due to a customer-side typo, a credit gift may be issued to allow republishing. Standard gift in these cases is 150 HDCs (sufficient to republish corrected PRs). - Credit refunds are discretionary and reviewed case-by-case. Refunds are not guaranteed for PRs that have already fully published. - Customers should request the credit refund in the same support ticket where the retraction is requested. Important Notes - Always treat PR submission as final — review carefully before submitting. - Retraction is only possible while a PR is in 'Publishing' status, not after full publication. - Credit gifts (e.g., 150 HDCs) are intended to cover the cost of republishing the corrected version, not as compensation beyond that.

📣 Digital PR troubleshooting

Resolve the most common Digital PR errors in Search Atlas — from failed campaign creation and CSV imports to email spam filtering, stuck press releases, and incorrect citation data. ⚠️ Error 1: Creating a new campaign fails or shows no publication results What's happening: Campaign creation depends on the publication discovery index loading correctly. If the index is refreshing, filters are too restrictive, or the discovery service is temporarily unavailable, the campaign builder may return zero results. 1. Reload the page completely. 2. Wait 2–3 minutes and retry the search. 3. Use broader niche filters first — start with wide industries like health, finance, marketing, or technology. 4. Avoid stacking multiple filters simultaneously. 5. Remove advanced filtering temporarily. 6. Refresh the publication search panel. 7. Try a different browser session. 8. Confirm the campaign service is loading normally. 9. Contact support if all publication searches consistently return empty results. Note: Narrow filters are the most common cause of zero results. Publication databases refresh asynchronously, so a brief delay is normal. ⚠️ Error 2: Contact list import (CSV) is not loading contacts What's happening: CSV imports require exact column names and UTF-8 encoding. Files with renamed headers, extra columns, hidden formatting, or unsupported encoding may fail silently. 1. Download the official CSV template: Digital PR → Contacts → Import → Download Template. 2. Do not rename any columns. 3. Keep only supported fields and ensure these required columns exist: First Name, Last Name, Email. 4. Remove all blank rows. 5. Save the file as UTF-8 CSV. 6. Avoid Excel auto-formatting where possible. 7. Open the file in a plain text editor to verify formatting before importing. 8. Test with a small import batch first. 9. Contact support if properly formatted files still fail. Note: Header mismatches are the most common import failure. UTF-8 encoding prevents hidden character issues. ⚠️ Error 3: Outreach emails are going to spam for recipients What's happening: Cold outreach campaigns are heavily affected by spam filtering, domain reputation, email authentication, and bulk sending patterns. New sending domains are especially vulnerable. 1. Configure SPF records for your sending domain. 2. Set up DKIM authentication. 3. Verify DMARC settings if possible. 4. Avoid spam-trigger phrases such as: free, guaranteed, act now, limited time. 5. Personalize outreach emails using template variables. 6. Avoid sending identical emails to large batches. 7. Warm up new sending domains gradually. 8. Limit outreach volume initially. 9. Test deliverability with small campaigns first. 10. Use a dedicated outreach sending domain when possible. ⚠️ Error 4: Press release stuck in 'publishing' status for an extended period What's happening: Press releases may appear stuck in publishing status for 3–4 weeks or more, even after a distributor has already rejected them. This is a UI display issue — the interface fails to update the PR status after a rejection event. Digital Journal is a commonly observed rejecting distributor, though other partners may also reject submissions. 1. Confirm the PR has been in publishing status for more than 7–10 days. 2. Check the PR detail page for any distributor feedback or rejection notes. 3. Contact support with your campaign/PR ID so the team can verify the actual distributor status. 4. Request a status correction if the PR was silently rejected. 5. Request a Hyperdrive credit refund for rejected PRs (e.g., 200 Hyperdrive credits per rejected PR, depending on your plan). - The publishing status in the UI may not reflect the actual submission state — the underlying PR may already have been rejected. - Support can manually correct PR statuses and issue Hyperdrive credit refunds for rejected submissions. - Always include your campaign ID when contacting support to expedite the fix. ⚠️ Error 5: Local citation published with incorrect business information What's happening: Local citation submissions are distributed to third-party data aggregators (such as Dataaxle) that publish business information across directory networks. In some cases, the distributor may publish incorrect details — such as a wrong business name, phone number, or address — that differ from what was originally submitted. 1. Locate the affected campaign and note the campaign ID (e.g., id-6010). 2. Identify the specific distributor publishing the incorrect information (e.g., Dataaxle). 3. Capture screenshots or URLs showing the incorrect listing. 4. Compare the published data against your original campaign submission. 5. Contact support with the campaign ID, distributor name, and details of the incorrect information for escalation. - Third-party citation distributors may take time to correct published data even after escalation. - Support will escalate citation accuracy issues directly to the responsible distributor. - Always provide your campaign ID to ensure the correct submission record is reviewed. 🎯 You now have the steps to diagnose and resolve the most common Digital PR issues in Search Atlas. If a problem persists after following these steps, contact support with your campaign ID for direct escalation.

📰 Retract a Published Press Release from a Distributor

🔍 Overview Once a press release is published through Search Atlas PR Distribution, it is submitted to third-party distributors in your selected network. Because these distributors are external platforms, removal requires a manual retraction request — it cannot be undone from within the platform alone. This article explains what information to have ready and how to submit a retraction request through the support team. 📋 Before You Begin Make sure you have the following information ready before requesting a retraction: - The title of the press release you want removed. - The specific distributor you want it retracted from. - The reason for removal (e.g., outdated information, published in error, client request). Knowing these details in advance speeds up the process significantly. 🗂️ Step 1 — Locate Your Published Press Release 1. Navigate to the PR Distribution section of the platform. 2. Find the press release you want retracted and note its full title and the distributors it was sent to. 💬 Step 2 — Submit a Retraction Request Because retraction involves coordinating directly with the external distributor, this action must be handled by the Search Atlas support team on your behalf. 1. Contact the support team using the chat widget in the bottom-right corner of the platform. 2. Provide the following details in your message: - The exact title of the press release. - The distributor name. - Your reason for removal. Our team will log the request and contact the distributor directly to initiate the removal. ⏱️ What to Expect After You Request Removal Retraction timelines vary depending on the distributor's own editorial and publishing policies. Here is what typically happens: - Acknowledgement: The support team will confirm your request has been received and escalated. - Processing time: Processing timelines depend on the individual distributor's policies and are outside Search Atlas's direct control. - Status updates: The support team will communicate any updates as they become available. If you need a status update, reach out through the chat widget. 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 Press Release Link Popups

🔍 What causes the issue? When you add a hyperlink in the press release editor, the link window may open partially outside the browser window. This can make the fields and controls difficult or impossible to use. A separate survey or overlay may also cover the editor controls. ⚙️ Try these quick fixes 1. Close any overlay: Dismiss survey messages or pop-ups covering the press release editor. 2. Reset browser zoom: Set your browser zoom to 100% using the browser menu or Ctrl+0 on Windows or Command+0 on Mac. 3. Resize the window: Maximise your browser window, then reload the press release editor. 4. Scroll to the editor toolbar: If the toolbar is out of view, scroll within the editor until the link tool is visible before selecting it. 5. Try the link tool again: Select the text, choose the hyperlink option, and enter the destination URL. 📝 Add the hyperlink Highlight the words that should become clickable, select the link or URL tool, and enter the full web address, including https://. Confirm the link, then continue through the press release form and save your changes. 🔄 If the popup remains off-screen - Refresh the page and reopen the press release editor. - Try a private or incognito browser window. - Temporarily disable browser extensions that modify pages or display surveys. - Try a different supported browser or display resolution. These steps can restore the popup position and make the link controls accessible without changing your press release content. 💬 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.

🛠️ Fixing Incomplete Press Release Distribution

If your press release shows distribution to only a small number of sites — for example, 15 outlets instead of your full network — there are a few common causes. Most can be identified and resolved directly in the platform. This guide walks you through how to check your distribution status, confirm the count, and take corrective action when needed. 🔍 Why Your Coverage Count May Look Low Before assuming something went wrong, review the most frequent reasons a distribution shows limited site coverage: - Distribution is still in progress. Press releases roll out in waves. Full coverage can take up to 72 hours to complete, so an early check may show only a partial count. - The release was scheduled, not sent immediately. Scheduled or upcoming releases do not begin distributing until their launch time passes. - A limited distribution option was selected. Depending on the package chosen at submission, your release may target a smaller network of outlets. - Some outlets declined or filtered the content. Individual networks can reject releases based on editorial rules, restricted industries, or content guidelines. - Stats were viewed mid-update. Publication reports refresh periodically, so numbers can temporarily appear incomplete or inconsistent. ✅ Check Your Distribution Status Use the Step 4 Distribution & Status drawer to review the real-time state of your release: 1. Open your press release from the main Press Releases table. 2. Navigate to Step 4, Distribution & Status. 3. Open the status drawer to see the full list of targeted outlets and each one's current state (pending, published, or declined). 4. Confirm the release has launched. Releases still marked as upcoming or scheduled are excluded from active distribution until their start time. 5. Compare the total number of targeted outlets against the number marked as published. If most outlets show a pending state, your distribution is still running — allow the full rollout window to finish before taking further action. 🛠️ How to Correct Incomplete Coverage If the distribution window has closed and coverage is still incomplete, follow these steps: 1. Confirm your selected distribution package. Review the submission summary to verify which network tier was chosen. If a smaller package was selected by mistake, you can resubmit the release with the expanded option. 2. Review declined outlets. The status drawer shows which outlets declined the release and why. Addressing the flagged issue, such as editing restricted content, allows you to resubmit. 3. Resubmit the release. After making corrections, resubmit from the press release editor. The new distribution begins within a few minutes and follows the standard rollout window. 4. Verify results in the stats report. Once redistribution completes, check the publication report to confirm the updated count. Each outlet is counted once per successful publication. 📊 Reading Publication Stats Correctly Publication counts reflect outlets that have successfully published your release. Keep these points in mind: - Counts update as outlets publish, not all at once — expect the number to grow during the rollout window. - Declined outlets are listed separately and do not count toward published totals. - If a release has multiple distribution runs, the report reflects the most recent completed run. If numbers still look wrong after the full window has passed, refresh the report page before escalating further. 💡 When to Contact Support Contact support if any of the following apply: - More than 72 hours have passed and the distribution count has not changed. - The status drawer shows an error or a stalled distribution. - Published outlets are missing from your stats report. - You resubmitted a release and it did not redistribute. 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.

⚠️ Press Release Image Upload — WEBP Publish Error (Resolved)

We're aware of an issue in the Press Release editor where uploaded JPG or PNG images were silently converted to WEBP during upload, causing a publish error even though the original file was in a supported format. This issue has been resolved — re-uploading your image in the draft editor is all it takes to publish successfully. 🔍 What's Happening When you uploaded a JPG or PNG to a Press Release draft, the editor silently converted the image to WEBP format. When you then tried to publish, Signal Genesys — the press release distribution platform — rejected the file with this error: "WEBP is not supported by Signal Genesys. Please upload JPG or PNG." Because no warning appeared during upload, the error at publish time was unexpected. Any press release draft where an image was uploaded before the fix was deployed may show this behavior. 🛠️ Workaround Steps Re-uploading your image inside the draft editor resolves the issue. The fix is now live, so your file will retain its original format. 1. Open the affected Press Release draft. 2. In the Press Release editor, click the image thumbnail or the image upload area to open the image selector, then remove the current image. 3. Re-upload your original JPG or PNG file. 4. Publish your press release. After completing these steps, your press release will publish without the WEBP format error. 📡 Engineering Status This issue is fully resolved. The Press Release editor now passes the file's original format directly to Signal Genesys instead of converting it to WEBP. JPG and PNG are confirmed supported end-to-end. The fix is live for all customers and no further customer action is required beyond re-uploading affected images. ⚠️ Known Issue: Publish-Time HTTP 500 Separately, we are tracking an active HTTP 500 error on the Signal Genesys publish endpoint that can prevent some publishes from completing even after the WEBP issue is resolved. This is under investigation. If you still cannot publish after re-uploading your image, please contact support so we can investigate. This article will be updated once that fix ships. 🚧 Other Publish Errors If you encounter a different publish error, the following are the most common cases and what to do: - 401 API Token invalid — Verify that your Signal Genesys API key is correct and is not a placeholder value. If you do not have a valid key, contact your account manager or reach out via the Authority Building support channel to request one. - Proxy / image-fetch errors (407) — These can appear when the publish flow fetches images from Brand Vault. Retry the publish, and contact support if the error persists. - Temporary API downtime or "fetching image size" loops — These errors are usually transient. Wait a few minutes and try again; if it continues, contact support. 📊 Dashboard Status Sync Delay After a successful publish, the distribution dashboard may briefly show a "failed" status due to a synchronization delay between Signal Genesys and our reporting. Wait a few minutes and refresh the page before contacting support. Credits are automatically refunded for genuine failures. 📞 When to Contact Support If re-uploading your image does not resolve the publish error, contact our support team. When you reach out, include: - The name of the affected press release draft. - A screenshot of the error message you're seeing. - The file format of the image you're uploading (JPG or PNG). Our team will investigate and follow up with you directly. 🎯 The image format issue in the Press Release editor is fully resolved. Re-upload your JPG or PNG in the draft editor and your press release will publish without error — if you're still seeing issues, our support team is ready to help.

📰 Press Release Multi-Location Publishing and Website Integration

🗺️ Overview Search Atlas Press Release distribution supports multi-location businesses. If you manage several Google Business Profile locations, you can publish targeted press releases for each one and display those releases directly on your website. This article explains how both features work together. 📍 Managing Press Releases Across Multiple Locations Yes, you can create and manage separate press release campaigns for each of your business locations. Here is how it works: 1. Log in to your Search Atlas account and navigate to the Press Release section from the left sidebar. 2. When creating a new press release, look for the Location field during the setup process. 3. Select the specific Google Business Profile location this press release applies to. Each location you have connected to your account will appear in the dropdown. 4. Complete the rest of the press release details — headline, body copy, contact information, and distribution options — as you normally would. 5. Repeat this process for each location. Each press release is stored and tracked independently, so you can monitor performance per location. Important: Make sure all five of your Google Business Profile locations are connected to Search Atlas before you begin. If a location is missing from the dropdown, check your Google Business Profile integration settings. 🌐 Embedding Published Press Releases on Your Website Once a press release is published, you can feature it on your website in an "In the News" section using Search Atlas Website Studio. Follow these steps: 1. In the left sidebar, go to Website Studio (URL: /website-studio). 2. Open the page where you want to display your press releases — for example, a dedicated News or Media page. 3. Add a new content block or section to the page and choose the Press Release widget or embed block from the element library. 4. Configure the block to pull in your published press releases. You can filter by location if you want a location-specific feed, or display all published releases site-wide. 5. Customise the layout, heading, and styling to match your website design. 6. Click Save and then Publish to make the changes live. Your "In the News" section will automatically update as you publish new press releases, so you do not need to manually add each one to the page. 💡 Tips for Multi-Location Businesses - Use clear, location-specific headlines so visitors and search engines understand which area each press release targets. - Tag each press release by location during creation to keep your dashboard organised when you manage five or more profiles. - Create a separate News page per location in Website Studio if you run distinct websites or landing pages for each branch — then filter the embed block to show only that location's releases. - Monitor distribution reports for each press release individually to compare coverage across your locations and identify which topics drive the most pickups. ❓ Frequently Asked Questions Can I publish the same press release to all five locations at once? Currently, each press release is created for a specific location. If you want to cover all five locations, you will need to create five separate press releases — one per location. This ensures each release contains accurate, location-specific details that resonate with local audiences and local distribution outlets. Will the embedded press releases on my website affect my SEO? Yes, positively. Featuring published press releases on your website adds fresh, keyword-rich content and creates internal links. Combined with the external backlinks generated by distribution, this strengthens your overall SEO profile. What if my press release is not showing up in the Website Studio embed? Check that the press release status is Published and not still in Draft, Generating, Generated, Publishing, Publish Stuck, or Publish Failed. Only fully published releases appear in the embed feed. 🆘 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.

🛠️ Resolving Errors When Publishing a Press Release

If you see an error when publishing a Press Release, it usually means a required field is missing, the content does not meet distribution guidelines, or your account is short on credits. This guide walks you through the most common causes and how to fix each one so your release publishes successfully. ✅ Before You Start Most publishing errors can be prevented by confirming a few basics first: - You are signed in to the correct workspace. - Your subscription is active and you have at least one available Press Release credit. - Your release includes a title, body content, and a target URL. - Your internet connection is stable. 🔧 Common Errors and How to Fix Them 1️⃣ Missing or Incomplete Required Fields This is the most frequent cause of a failed publish. The system blocks submission if any required field is empty. 1. Open your Press Release draft. 2. Check that the title, summary, and main body are all filled in. 3. Confirm you have added at least one valid anchor text and target URL. 4. Confirm the country field is set, as it is required for distribution. 5. Make sure the target URL begins with https:// and points to a live, public page. 6. Save your changes and try publishing again. If you receive an error stating the country field is empty even though it is filled in, this was a known issue that has since been fixed. Refresh the page and try publishing again, and contact Search Atlas Support if it persists. 2️⃣ Content Does Not Meet Distribution Guidelines Press Release distribution networks (Signal Genesys) apply editorial standards. Releases may be rejected if they contain prohibited content. - Remove promotional or sales-heavy language (for example, "buy now" or pricing-only content). - Avoid adult, gambling, or other restricted topics. - Ensure the content is original and written in a news or announcement style. - Keep the body within the recommended word count (typically 400–800 words). - Check that links point to legitimate, working pages and not redirects or shorteners. 3️⃣ Insufficient Credits or Plan Limits Publishing requires available Press Release credits. The number of credits required depends on the distribution channel you select (for example, some channels cost more credits than others), so a release that needs more credits than you have available will fail, often with the message "Signal Genesys: Insufficient credits!". 1. Open your account billing or usage page. 2. Review your remaining Press Release credits and compare them to the credits required by your chosen distribution channel. 3. If you have too few, upgrade your plan or purchase additional credits. 4. Return to your draft and publish once enough credits are available. 4️⃣ Invalid or Unreachable Target URL If the URL you are linking to cannot be reached, the release will not publish. - Open the target URL in a new browser tab to confirm it loads. - Remove any password protection or "noindex" restrictions on the page. - Replace any broken or staging URLs with a live, public address. 5️⃣ Image Upload Errors An oversized, unsupported, or missing image can stop publishing. - Use PNG or JPG format. - Keep the file under 2 MB and at least 300×300 pixels. - Re-upload the image and confirm it appears in the preview before publishing. You may occasionally see "WEBP is not supported by Signal Genesys. Please upload JPG or PNG" even when your original image is a JPG or PNG. This happened because AI-generated or imported images were sometimes stored internally as WEBP. This has been fixed so eligible images are converted automatically; if you still see it, re-upload the image and try again. If you see "Missing images: The press release requires at least one image in order to be deployed" even though images are present, this could occur when images were added to the Knowledge Graph after the release content was generated. This has been resolved so images on the linked Knowledge Graph are now picked up at publish time. If you encounter it on an older draft, open the editor and re-attach the image before publishing. 6️⃣ Session Timeout or Temporary Glitch Occasionally an error is caused by an expired session or a brief connection issue. 1. Refresh the page and confirm you are still signed in. 2. Clear your browser cache or try an incognito/private window. 3. Switch to a supported browser such as Chrome or Firefox. 4. Attempt to publish again. 7️⃣ Distribution Channel Not Available If a previous publish attempt failed partway through, a leftover "coming soon" distribution channel can be attached to your release and cause a retry to fail with an error such as "Distribution channel <name> is not available" — even though you never selected that channel. - This has been fixed so unavailable "coming soon" channels are excluded automatically, and retrying the publish should now succeed. - If you still see this error, contact Search Atlas Support with your draft details so the stale channel can be cleared. 💬 Still Seeing an Error? If you have worked through the steps above and the release still will not publish, gather a few details to help our team resolve it faster: - The exact error message text (a screenshot is ideal). - The name or ID of the Press Release draft. - The date and time you attempted to publish. - The browser you are using. Send these details to Search Atlas Support through the in-app chat or your support email, and our team will investigate and help you publish your release.

📰 Fix Press Release Category Before Distribution

🔍 Overview When you distribute a press release through Search Atlas, the category you select is permanently locked once the release is submitted for distribution. This means it cannot be changed after the press release has been sent out. Understanding this limitation before you submit will save you time and help ensure your release reaches the right audience. ⚠️ Why Categories Cannot Be Changed After Distribution Once a press release is submitted, it is immediately processed and forwarded to the distribution network. Because the release has already been accepted and published, Search Atlas has no ability to edit or update the category retroactively. ✅ What You Can Do If you submitted a press release with the wrong category, here are your options: - Accept the current categorisation: If the content of your press release is still relevant to the published category, the release may still perform well. Readers and search engines also rely on the body text to understand the topic, not only the category label. - Submit a new press release: If the wrong category significantly misrepresents your business or content, the most effective solution is to create and submit a new press release with the correct category selected. You can use the same or revised content. - Contact support for guidance: In some circumstances our team may be able to advise on the best course of action for your specific situation. See the section below on how to reach us. 🛡️ How to Avoid Category Mistakes in the Future Follow these steps before submitting any press release to make sure the correct category is selected: 1. Review the category field carefully during the press release creation process. Do not rely on a default pre-filled value without confirming it matches your industry or topic. 2. Check the available categories before finalising your selection to find the most accurate match for your business type. 3. Read through all fields before completing your submission, including the category, headline, and target outlets. 4. Ask a colleague to review it if the press release is high priority. A second set of eyes can catch errors before they become permanent. 📋 Frequently Asked Questions Can Search Atlas update the category on my behalf after distribution? No. Once a press release has been submitted and distributed, the category cannot be changed. If the wrong category was selected, the recommended course of action is to submit a new press release with the correct category. 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 Press Release Summary Word-Count Publish Error

🔍 What Is This Issue? When publishing a press release in PR Distribution, some users see an error reading 'The blog summary must contain at most 45 words' even when their summary is 45 words or fewer. This is caused by a known discrepancy between the word counter displayed in the editor and the stricter validation check that runs at the moment of submission. The editor may show your summary as compliant, but the final check can count words differently and block publishing. ⚙️ Step 1: Try a Clean Browser Session Before anything else, rule out a browser caching issue: 1. Clear your browser cookies and cache. 2. Open a private or incognito window. 3. Navigate to Left sidebar → Authority → PR Distribution. 4. Reopen your press release and attempt to publish again. In some cases this alone resolves the error. If the error persists, continue to Step 2. ✂️ Step 2: Reduce Your Summary Below 44 Words Because the editor's word counter and the submission validator can disagree, the reliable workaround is to keep your blog summary noticeably under the stated 45-word limit. Aim for 43–44 words or fewer to give enough margin for both counters to agree. 1. Open your press release in Left sidebar → Authority → PR Distribution. 2. Locate the blog summary field. 3. Edit the summary so it is 43–44 words at most. Remove filler phrases, conjunctions, or secondary details to trim the count without losing meaning. 4. Save your changes, then attempt to publish again. This has resolved the issue for most affected users. If publishing still fails after trimming to 43 words or fewer, move to Step 3. 💡 Tips for Counting Words Accurately - Paste your summary into a plain-text editor (such as Notepad or TextEdit) and use that tool's word count rather than relying solely on the in-editor counter. - Hyphenated compounds (e.g. AI-generated) may be counted as one or two words depending on the validator — split or merge them to test. - Avoid trailing punctuation or line breaks that could affect how words are parsed at submission. 📊 Known Engineering Status This word-count validation discrepancy was identified and a fix was filed with the engineering team (ticket #109383477). A related fix addressing blog summary word-count validation has been marked as resolved for affected accounts. If you are still experiencing the error after following the steps above, your account may need to be reviewed individually by the engineering team. 🚀 Still Blocked? Escalate With a Screen Recording If reducing your summary to 43 words or fewer and using an incognito session does not resolve the issue, the engineering team will need a recording to investigate further. Before contacting support, prepare the following: - A screen recording that shows your summary text, the word count visible in the editor, and the error message that appears when you click publish. - The exact word count of your summary (verified in a plain-text editor). - The title of the affected press release. 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 Press Release Payment Errors and Image Upload Issues

Overview A common issue arises when publishing press releases in Search Atlas: unexpected payment errors even when your account shows available credits, as well as problems uploading images within the press release editor. Both of these issues require backend investigation by our support team. This article explains what is happening and how to escalate efficiently so our team can resolve it for you. Why You're Seeing a Payment Error A payment error during press release publishing does not always mean your credits are insufficient. There may be an issue with the payment method associated with your account, or the way press release billing interacts with your credit balance. Because the exact cause varies by account, our support team will need to investigate directly. There are no self-serve steps that will reliably resolve this — the fix must be applied on the backend. Image Upload Problems in the Press Release Editor Some users also experience issues uploading images while building their press release. Image upload failures in the press release editor are also backend issues that our team must investigate directly. While there is no guaranteed self-serve fix, you can check the following before reaching out, as this information will help our team diagnose the issue faster: - Confirm your image is in a standard web format (JPG, PNG, GIF, or WebP) — non-standard or corrupted files may fail to upload - Keep file size as small as practical; very large files are more likely to encounter upload errors - Test whether the issue occurs with a different image file to determine if the problem is file-specific or affects all uploads - Note the exact error message displayed at the time of the upload attempt If the issue persists after checking the above, our support team will need to investigate your account configuration or a broader platform problem directly. How to Get Help If you encounter a payment error or an image upload issue while trying to publish a press release, please have the following ready when you reach out: - Your Search Atlas account name - The exact error message you received (copy it verbatim if possible) - The name or title of the press release you were trying to publish - The date and approximate time the error occurred - For image upload issues: the file format, file size, and whether the problem affects all images or specific ones Providing these details upfront will allow our team to identify the root cause and resolve your issue without unnecessary back-and-forth. 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 Press Release Publishing Errors Fast

Overview When a press release fails to publish, a common root cause is an insufficient Hyperdrive credits error. If your account does not have enough Hyperdrive credits, publishing will be blocked. Use this article to understand what is happening and how to resolve it. Why Publishing Fails: Hyperdrive Credits Publishing a press release in Search Atlas consumes Hyperdrive credits. If your account balance does not have enough credits to cover the action, the publish will not go through. This is a billing-related block — your content itself may be perfectly valid, but the action cannot complete without sufficient credits. How to Resolve an Insufficient Credits Error To unblock publishing, you will need to purchase additional Hyperdrive credits through your account's billing settings. Follow these steps: 1. Navigate to the Billing section from the top-right avatar (Avatar Menu (👤)) of your Search Atlas account. 2. Review your current Hyperdrive credit balance to confirm it is too low to complete the publish action. 3. Purchase additional Hyperdrive credits through the available options in the Billing section. 4. Once the credits have been added to your account, return to your press release draft and attempt to publish again. If you are unsure how many credits are required to publish a press release, or if you have purchased credits and publishing is still blocked, please have the following ready before contacting support: your account or project name, the exact error message you see on screen, and the approximate date and time of the failed publish attempt. 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.

📰 Track Your Press Release Google Indexing Status

🔍 Overview After publishing a press release through Search Atlas PR Distribution, one of the most common questions is: "Has Google indexed my press release yet?" This article explains how to check indexing status, how long indexing typically takes, and what to do if your PR hasn't been indexed after several weeks. 📋 Where to Find Your Press Release Status To view the current status of your published press releases, log in to Search Atlas and navigate to Authority → PR Distribution (Press Releases) in the left sidebar. Locate your submitted press release in the list to see its current distribution and publication state. This area is your central hub for monitoring all submitted press releases and their distribution progress. ⏱️ How Long Does Google Indexing Take? Google indexing is controlled entirely by Google's crawling schedule — Search Atlas cannot force or guarantee a specific indexing timeline. Indexing can take anywhere from a few days to several weeks depending on a number of factors: - Site authority: The authority of the sites that picked up your PR influences how quickly Google crawls and indexes those pages. - Crawl frequency: How often Google visits the domains that syndicated your press release affects discovery speed. - Crawl queue demand: Overall demand on Google's crawl queue at any given time can slow or accelerate indexing. If you submitted your press release recently, waiting several weeks before concluding there is a problem is generally recommended — a delay does not necessarily indicate an issue. ✅ How to Manually Verify Indexing on Google You can verify whether Google has indexed your press release at any time using these methods: 1. Open a new browser tab and go to google.com. 2. In the search bar, type site: followed by the exact URL of your published press release (for example: site:example.com/your-press-release-url). 3. If Google returns a result for that page, your PR has been indexed. 4. Alternatively, search for a unique phrase or headline from your press release in quotation marks (for example: "Your Exact Press Release Headline Here") to find syndicated versions that have been indexed. This method works for both your primary press release URL and any syndicated versions picked up by news sites in the distribution network. 🛠️ What to Do If Your Press Release Has Not Been Indexed If a significant amount of time has passed and your press release still does not appear in Google search results, here are the steps to take: 1. Confirm the press release was successfully submitted and distributed by checking its status under Authority → PR Distribution (Press Releases) in the left sidebar of Search Atlas. 2. Use the site: search method described above to verify indexing directly on Google. 3. Check Google Search Console (if you have access) for the specific URLs where your PR was syndicated to see if any crawl errors or indexing issues are reported. 4. If you have confirmed distribution was successful but indexing has not occurred after an extended period, contact the Search Atlas support team with your press release details so they can investigate further. 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.

📰 How to Request a Press Release Retraction

📋 Overview Once a press release is submitted through Search Atlas PR Distribution and published by a third-party distributor, the content is live on that distributor's network. Retractions are not guaranteed, but you can formally request one. This article explains the process, what to expect, and how our team can help. ⚠️ Important: What You Should Know Before Requesting a Retraction Please read the following carefully before proceeding: - Retractions are not guaranteed. Once a press release is published by a third-party distributor, that distributor controls whether the content is removed. Search Atlas can submit a retraction request on your behalf, but the final decision rests with the distributor. - Publication is final at the point of distribution. Distributors process and publish content automatically. There is no recall window after submission is confirmed. - Timing matters. The sooner you raise a retraction request after publication, the better the chances the distributor will act on it. Older publications are significantly harder to retract. - Partial removal is possible. Some distributors may remove content from their own site but cannot control syndicated copies picked up by other outlets. 🛠️ How to Submit a Retraction Request Search Atlas does not currently offer a self-serve retraction tool in the platform. To request a retraction, you must contact our support team directly so we can escalate to the distributor on your behalf. Follow these steps: 1. Open the chat widget in the bottom-right corner of the platform. 2. Type human teammate to be connected with a member of our team. 3. Provide the following details: - The full title of the press release. - The publication date. - The distributor name where you want the retraction submitted. - The reason for the retraction request. 4. Our team will log the request and contact the distributor. We will follow up with you once we have a response. ⏱️ Expected Timeline Response times vary by distributor. There is no guaranteed turnaround time, and our team will communicate any updates from the distributor as soon as they are available. 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 Signal Genesys Press Release Embed Code

📋 Overview If your press releases are not displaying on your website, or you are unsure where to find the embed code inside Signal Genesys, this article walks you through the exact steps to locate the snippet and resolve the most common loading issues. 🔍 Where to Find Your Press Release Embed Code Follow these steps to locate the embed code inside your Signal Genesys account: 1. Log in to your Signal Genesys account at app.signalgenesys.io. 2. In the left-hand navigation, click Media Room. 3. Select the Embed or Widget tab — the exact label may vary depending on your plan. 4. Copy the full code snippet displayed in the box. Make sure you copy everything from the opening tag to the closing tag without leaving anything out. 5. Paste the snippet into your website where you want the press releases to appear. If you use a CMS such as WordPress, paste it into an HTML block, not a plain text block. ⚠️ Common Reasons Press Releases Are Not Loading If you have already placed the embed code on your site but press releases are still not showing, check the following: - Outdated embed code: Signal Genesys periodically updates its embed system. If your code was copied several months ago, it may be pointing to a deprecated endpoint. Return to app.signalgenesys.io, generate a fresh snippet, and replace the old one on your website. - Incorrect paste location: The code must be placed inside an HTML-enabled section of your page. Pasting into a plain-text or visual editor field will break the script. - Content Security Policy (CSP) blocking the script: Some websites have security rules that block third-party scripts from running. Ask your web developer to whitelist the Signal Genesys domain in your site's CSP headers. - Browser cache: After updating the embed code, clear your browser cache or test in a private/incognito window to confirm the new code is loading. - Ad blockers or script blockers: Browser extensions can prevent the widget from rendering. Test in a clean browser profile with extensions disabled to rule this out. - Press releases not yet published: The embed widget only displays press releases that have been fully published inside Signal Genesys. Draft or scheduled releases will not appear. ✅ Step-by-Step: Replace an Outdated Embed Code 1. Log in to app.signalgenesys.io. 2. Navigate to Media Room > Embed / Widget. 3. Copy the current code snippet. 4. Open your website's backend or CMS. 5. Find the page or template where the old snippet was placed. 6. Delete the old code completely and paste the new snippet in its place. 7. Save and publish the page. 8. Open the page in an incognito browser window to confirm press releases are now loading. 🛠️ Quick Checklist Before Contacting Support - Confirmed the snippet was copied from app.signalgenesys.io today (not weeks ago). - Pasted into an HTML block, not a plain-text field. - At least one press release is fully published in Signal Genesys. - Tested in an incognito window with browser cache cleared. - Tested with browser extensions disabled. - Asked your developer to check for CSP restrictions if the issue persists on a custom site. 💬 Still Need Help? If you have followed all the steps above and press releases are still not loading, 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.

📣 Signal Genesys (Press Release Distribution & GBP Deployment)

Use this article to diagnose and fix the most common Signal Genesys distribution failures — press releases stuck in Pending, AI summaries rejected for length, and API token errors when publishing a press release. Signal Genesys distribution depends on backend validation, outlet syndication queues, entity verification, external publisher acceptance, Google indexing, and API synchronization between Search Atlas and Signal Genesys. Because distribution spans multiple third-party systems and publishing partners, some delays and partial propagation are expected. ⚠️ Error 1: Press Release Stuck in "Pending" and Not Distributing This is the highest-volume Signal Genesys issue (41,000+ occurrences). The distribution service rejects a press release when required fields fail backend validation. Common causes include missing fields, invalid formatting, summaries exceeding limits, invalid scheduling dates, incomplete contact information, or malformed company profiles. How to fix it: 1. In the Search Atlas left sidebar, go to Authority → PR Distribution (Press Releases) → [Your PR] → Edit. 2. Confirm all required fields are completed: headline, body, summary, company name, contact details, and website URL. 3. Ensure the body contains at least 300 words. 4. Confirm the summary is under 45 words. 5. Verify the scheduled distribution date is not in the past. 6. Remove unusual formatting or unsupported symbols. 7. Save the press release again before resubmitting. 8. Retry distribution after refreshing the dashboard. 9. Test with a simplified version of the press release if validation keeps failing. 10. Contact support if the press release stays stuck longer than 2 hours. Validation failures happen before distribution begins, so saving and resubmitting often refreshes invalid backend states automatically. When all required fields are complete and valid, distribution proceeds normally. Visual status glitch on "publishing" If your press release appears stuck on "publishing" or "publishing content" for more than a few hours, it may have failed validation even though the UI did not update. Refresh the dashboard or open the PR details. If the status has not changed after 24 hours, contact support for backend verification. ⚠️ Error 2: AI Summary Rejected — "Must Contain at Most 45 Words" Signal Genesys enforces a strict 45-word limit for press release summaries. AI-generated summaries occasionally exceed this limit even when they look short on screen. How to fix it: 1. Open Edit Press Release → Summary. 2. Count the words manually. 3. Reduce the summary to 45 words or fewer. 4. Write one concise sentence that covers what happened, who is involved, and why it matters. 5. Remove filler language and marketing phrases. 6. Use the company name only once. 7. Save the summary before resubmitting. 8. Re-run AI summary generation if it is available. 9. Contact support if valid summaries keep failing validation. Word count validation is strict and automated, and hyphenated words may count differently depending on formatting. Once the summary is within the 45-word limit, the press release proceeds to distribution. 🔑 Error 3: "Invalid Scope Provided — Check API Key Permissions" This error indicates a platform-level API permission mismatch between Search Atlas and Signal Genesys. It is not caused by your account settings. How to fix it: 1. Refresh the Signal Genesys dashboard and retry distribution. 2. Confirm you are signed in to the correct Search Atlas account. 3. Complete the steps in the next section to remove and re-check your Signal Genesys API token. 4. Contact support if the error persists after re-checking your token. Once the correct API token is in place and permissions match, distribution resumes normally. 🔑 Signal Genesys API Error When Publishing a PR — Remove and Re-Check Your API Token If you get a Signal Genesys API error while publishing a PR article (including categories such as pop culture), the most common cause is an incorrect or stale API token. Removing the token and re-running the PR with the correct token resolves it in most cases. How to fix it: 1. Open your Signal Genesys integration settings where your API token is stored. 2. Remove the existing API token. 3. Confirm you have the correct Signal Genesys token — using a token from another service or account triggers this error. 4. Re-enter the correct token and save. 5. Run your PR again. 6. Contact support if the API error continues after re-checking the token. Our engineering team is actively investigating the root cause of this API error under ticket SPE-868. If removing and re-adding the correct token does not resolve it, reach out to support and reference SPE-868 so we can link your case to the investigation. ⚠️ "Please Fill Knowledge Graph's Website in Order to Deploy" If you receive "Please fill knowledge graph's Website in order to deploy" even though you already completed the Knowledge Graph website field: 1. Re-save the Knowledge Graph entry. 2. Wait 2–3 minutes for synchronization. 3. Create a new press release draft. If the error persists, contact support. ✅ Known Issue (Resolved): Duplicate Headline Detection If the system rejects your press release as a duplicate headline even after you change the headline, this was caused by a validation cache bug (ticket AB-1059). Confirm you are running the latest version of Signal Genesys; if the issue persists, contact support. 🎯 You now know how to clear a Pending press release, fix a rejected 45-word summary, and resolve Signal Genesys API token errors by removing and re-checking your token. If your PR still fails to publish after these steps, contact Search Atlas support and reference SPE-868 for the latest status.

📢 Fix Press Release Category Selection Before Publishing

🔍 Overview When you submit a press release through Search Atlas PR Distribution, the category you select at the time of submission is permanent. Once your press release is distributed to outlets such as USA Today, AP News, or other syndication partners, neither the category nor other core distribution settings can be changed or reassigned. This article explains why this limitation exists and what steps you can take to handle this situation. ⚙️ Why Categories Cannot Be Changed After Submission Press release distribution works by immediately syndicating your content to a network of publishers. The moment you click Publish, your press release is transmitted to partner outlets along with all the metadata you provided — including the category. Each publisher ingests and indexes this data in their own systems, which are outside Search Atlas's control. Because the content already lives on third-party platforms, retroactive edits to the category are not technically possible from our end. This is an industry-wide constraint across all press release distribution platforms, not a limitation unique to Search Atlas. ✅ How to Select the Right Category Before Publishing Follow these steps every time you create a new press release to make sure you choose the correct category: 1. In the left sidebar, go to Authority → PR Distribution. 2. Click New Release to open the submission form. 3. Fill in your headline, body content, and all required fields. 4. Locate the Category dropdown. Scroll through the full list carefully — do not rely on the default pre-selected option. 5. Select the category that most closely matches your business or the subject of your press release (for example, Home Cleaning Service rather than the default Apps and Software). 6. Review all fields one final time before clicking Publish content. Important: Treat the review step as mandatory. Once you click Publish, the submission is final and cannot be recalled or edited. 🛠️ What to Do If You Already Published With the Wrong Category If your press release has already been distributed with an incorrect category, here is what you should know: - The existing distribution cannot be edited or deleted. The syndicated content will remain live on partner outlets under the category selected at submission. - You may submit a new press release with the correct category. This will be treated as a fresh distribution and will use additional press release credits from your plan. - The incorrectly categorised release will not be removed from publisher sites, as Search Atlas does not control third-party editorial systems. Before submitting a new press release, review the content carefully to ensure it is not a duplicate of the original, as some outlets may flag near-identical submissions. 💡 Best Practices to Avoid Category Mistakes - Do not rush the submission form. Read each field label carefully, especially the Category dropdown, before proceeding. - Search for your industry keyword in the category list rather than scrolling through the full dropdown — many lists are long and the default selection may not reflect your business. - Use a pre-publish checklist. Before clicking Publish, confirm: headline, body copy, target URL, category, and distribution outlets are all correct. - If you are unsure which category applies, consult your marketing team or refer to how your business is classified on major directories before submitting. 📊 Understanding the Submission Workflow To help you visualise where the point of no return occurs, here is the standard PR Distribution workflow inside Search Atlas: 1. Draft — You enter the press release details and select settings including category. 2. Review — The final opportunity to check all fields for accuracy. 3. Publish — You click Publish content. The press release is immediately sent to the distribution network. 4. Published — The release appears under the Published tab in Authority → PR Distribution. At this stage, all settings are locked and distribution is complete. The transition from step 3 to step 4 is instantaneous. There is no queued state where edits are still possible after clicking Publish. 🆘 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.

🗺️ Embedding Google Maps Links in Press Releases

🔍 Overview When creating a press release in Search Atlas, you may encounter an error when trying to include a Google Maps link. This usually happens because Google Maps URLs contain special characters or tracking parameters that the press release editor does not accept. This article explains the correct link format to use so your press release publishes without issues. ⚠️ Why Google Maps Links Cause Errors Google Maps URLs come in several formats, and not all of them are compatible with the Search Atlas press release editor. The most common causes of link errors include: - Long dynamic URLs — These contain many parameters (such as @, !, and 1m fragments) that can break the link field validation. - Shortened URLs (maps.app.goo.gl) — These redirect URLs may not be recognised as valid by the editor. - Embedded iframe code — Pasting raw iframe HTML from Google Maps is not supported in the link field. - Copied browser address bar URLs — These often include session-specific parameters that cause validation failures. ✅ How to Get the Correct Google Maps URL Follow these steps to obtain a clean, compatible Google Maps link: 1. Open Google Maps in your browser and search for the location you want to link to. 2. Once the location is displayed, click the Share button (the arrow icon) on the location card. 3. In the Share panel, select the Copy link option. This generates a clean, shortened link in the format https://maps.app.goo.gl/XXXXXXX. 4. If the shortened format does not work in the editor, switch to the Send a link to your phone tab, copy the URL shown there, or use the Embed a map tab to find the plain URL within the iframe code (the value inside src="..."). 5. Paste only the plain URL (not any surrounding HTML) into the link field in your press release. 🛠️ Adding the Link in Your Press Release Once you have the correct URL, follow these steps inside Search Atlas: 1. Navigate to Left sidebar → Authority (Press Releases) to open the press release editor. 2. Select the press release you are working on, or create a new one. 3. Highlight the text you want to hyperlink, then click the Insert Link icon in the editor toolbar. 4. Paste the clean Google Maps URL into the URL field. 5. Click Apply or Save to confirm the link. 6. Preview the press release to verify the link appears and resolves correctly before publishing. 💡 Best Practices for Location Links - Always test your Google Maps link in a private browser tab before adding it to a press release to confirm it loads the correct location. - Use a descriptive anchor text such as "View our location on Google Maps" rather than pasting the raw URL as visible text. - Avoid copying URLs directly from the browser address bar — always use the Share → Copy link flow in Google Maps. - If you need to link to a specific business, search for the business by name in Google Maps rather than navigating by coordinates, as name-based links tend to produce cleaner URLs. 🆘 Still Seeing an Error? If you have followed the steps above and are still experiencing a Google Maps link error in your press release, 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. Additional Notes Extract the URL from the iframe src attribute: copy only the URL between the quotation marks after src=, starting with https://www.google.com/maps/embed?pb=. Do not include the surrounding quotes or any other part of the iframe tag.

📰 Publish and Embed Press Releases Across Locations

🗺️ Overview The Search Atlas Press Release (PR) tool supports multi-location businesses and includes website integration options. You can create separate PR accounts for each of your Google Business Profile locations and link your published press releases directly on your website — for example, in an In the News section. 📍 Creating PR Accounts for Multiple Locations If you manage multiple Google Business Profile locations, you can set up a dedicated PR account for each one. This keeps your press release activity organised by location and ensures each property is credited correctly during distribution. To get started with multi-location PR accounts, navigate to the Press Releases tool from the left sidebar. From there, look for the option to add or switch between location accounts. When creating or drafting a press release, make sure to associate it with the correct location so the right business details appear in the distribution. Each account operates independently, so press releases, distribution history, and performance data are tracked separately per location. If you are unsure how to set up or manage additional location accounts within the PR tool, our support team can walk you through the current workflow. Please have the following ready when you reach out: the business names and website URLs for each location you want to add. 🌐 Adding Published Press Releases to Your Website Once a press release has been published and distributed, you can link to it on your own website. This is a supported feature and a great way to build social proof in an In the News or Press section. The standard approach for adding published PRs to your site is: - Direct link: Copy the public URL of your published press release and add it as a hyperlink anywhere on your website. This works with any website platform. To locate the sharing options for a published press release, open the Press Releases tool from the left sidebar and find the press release you want to feature. Look for the sharing or link option associated with that press release, then copy the relevant URL and paste it into your website builder or CMS. If you cannot locate the link option for a specific press release, please contact our support team with the name of the press release and the date it was published so we can assist you directly. 📋 What to Have Ready When Contacting Support If you need hands-on help with multi-location PR setup or website linking, please have the following information available before reaching out: - The names and website URLs of each business location you want to add - The name and publication date of any press release you need help locating or linking 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.

📋 Press Release Publication Timeline and Review Phases

📋 Overview After you submit a press release through Search Atlas PR Distribution, it goes through several stages before it appears as published. One of the most important — and commonly misunderstood — stages is the auditorium review. This article explains what to expect during this process. ⏱️ Press Release Publication Phases Once you submit a press release, it moves through a processing and review pipeline before it is published. A key part of this pipeline is the auditorium review — an editorial review phase that takes place after your press release has been submitted and processed. - Submission confirmed: Your press release has been received and queued for processing. No action is needed on your end. - Auditorium review: This is a separate editorial review phase. During this phase, the press release is assessed before it goes live. This review is a normal, expected part of the process — it is not a sign that something has gone wrong. - Published: Once the auditorium review is complete, the press release is published and the status updates in your PR Distribution dashboard. 🔍 What Is the Auditorium Review? The auditorium review is an editorial checkpoint that occurs as part of the press release publication process. It exists to ensure that press releases meet the necessary quality and compliance standards before going live. Key facts about auditorium review: - It is a normal, expected part of the publication process. - You do not need to resubmit or take any action during this time. - Your dashboard status will not change until the review is complete and the release is approved for publication. 📅 When Will the Status Change? Your press release status in the PR Distribution dashboard will update automatically once the auditorium review is finished and publication is confirmed. You do not need to contact support to trigger a status change — it will update on its own. If your press release has been in auditorium review for an extended period and you have concerns, please reach out to our team with your press release ID and submission date so we can look into the status for you. 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 Press Release Validation Error in OTTO

What Is This Error? When ordering a press release inside an OTTO project, you may encounter a validation error related to the press release content type. This is a known issue that our team will need to investigate directly on your account. What to Have Ready Before Contacting Support - The name of the affected OTTO project - The exact validation error message you are seeing - The timestamp or date and time when the error occurred - Any screenshots of the error, if available What to Expect Because this error occurs at the account and project level, our support team will need to look into your specific OTTO project configuration to identify the cause and apply a fix. There are no self-serve steps available to resolve this error on your own at this time. 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.

How to Fix an Incorrect Date in a Press Release

If you see an incorrect or invalid date in your Signal Genesys press release, it is part of the body content — not a standalone scheduling field. You can correct it directly in the editor at any time before the press release is submitted for distribution. 📋 How Dates Work in Signal Genesys Signal Genesys does not include a scheduled publishing feature. When you click Publish, distribution begins immediately — there is no option to set a future release date. The date visible in your press release is typically an AI-generated line embedded in the body text, most commonly formatted as a FOR IMMEDIATE RELEASE header near the top of the document. Because this date is part of the body content, you have full control to edit or replace it while the press release remains in draft status. ✏️ Steps to Correct the Date 1. From your Search Atlas dashboard, navigate to Outreach > Press Release. 2. Locate your draft press release in the list and click it to open the editor. 3. Scroll to the top of the body content and find the date line — it is typically formatted as FOR IMMEDIATE RELEASE — [Date]. 4. Click on the date text and type the correct date in its place. 5. Review the full press release content for accuracy before proceeding. 6. Click Save to store your edits. 7. When you are ready to distribute, click Publish. Distribution begins immediately. ⚠️ Important Limitations - No scheduled publishing: Signal Genesys does not support future-date scheduling. Your press release goes live the moment you click Publish. - Distribution cannot be undone: Once a press release has been published, the distribution cannot be reversed, recalled, or re-dated. Verify all details — including the date — before submitting. - Editable fields before publishing: You can update the title, body content, summary, target URL, keywords, and AI writing instructions at any point while the draft is open. 💬 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.

📍 Geographic Targeting for Press Release Distribution

📋 Overview Search Atlas distributes press releases through established distribution channels rather than a geographic filter you apply manually. This article explains how the current system works and what options exist for reaching local or regional audiences. 🗺️ How Distribution Works When you create and publish a press release in Search Atlas, you select one or more distribution channels to publish through. You are choosing which networks carry your release — not a specific state, city, or region. There is currently no direct geographic or state-level targeting filter inside the platform. You cannot hand-pick a list of states or regions and restrict distribution to only those areas. 📡 The Closest Option: Local Distribution If reaching a local or regional audience is your goal, look for any locally focused distribution channel option available within your press release publishing workflow. Such channels typically distribute your release to a curated network of local and regional news outlets. Keep in mind: - What a local channel does: Distributes your press release to local and regional news outlets. - What a local channel does not do: Allow you to hand-pick specific states, cities, or individual outlets within that network. The local network is curated by the channel itself, not by you. Selecting a locally focused channel when publishing gives your release the best chance of appearing in regionally relevant outlets, but the exact geographic reach is determined by the channel's own network. 🚀 What to Do Right Now 1. Navigate to the press release distribution section of your Search Atlas account. 2. Start a new release or open an existing draft. 3. When choosing distribution channels, select any locally or regionally focused channel option if a local audience is your priority. 4. Consider combining a local channel with broader channels to maximize overall reach alongside local distribution. 🗓️ Roadmap: What's Coming Geo-targeted press release distribution — the ability to select specific geographic areas directly within the platform — is on the product roadmap as a planned feature. It is not available yet. We cannot confirm a release date at this time. 💡 Quick Reference Summary - State/region filter available now? No. - Closest current option? A locally focused distribution channel, which covers local and regional outlets. - Can I choose specific outlets? No — the network within each channel is curated, not user-selectable. - Is geo-targeting planned? Yes — it is on the roadmap, but no release date has been confirmed. 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 OTTO Press Release Draft Validation Error

🔍 What Is This Error? When ordering a press release through an OTTO project, you may see a validation error stating that no category is selected — even though a category appears to be chosen. This happens because the draft was saved before the Content Type field was fully completed. OTTO locks the required fields to that incomplete state, causing the error to persist on every subsequent order attempt. 📋 Why This Happens OTTO press release drafts require the Content Type field to be confirmed before the draft is saved or submitted. If you navigated away, refreshed the page, or clicked save while the field was still loading or unselected, the draft records an empty Content Type value internally — even if the field visually appears populated when you return to it. ✅ How to Fix the Error 1. In the left sidebar, click OTTO SEO, then open SEO Automation to access your OTTO dashboard (/seo-automation-v3). 2. Locate the affected OTTO project and open it. 3. Find the press release task showing the validation error and click into it to open the draft. 4. Delete the existing draft. Do not attempt to re-save or resubmit it — the incomplete state cannot be corrected by editing the saved draft. 5. Create a new press release draft from within the same OTTO project. 6. On the new draft form, fill in the Content Type field first, before entering any other information. Wait for the field to fully register your selection (the field label should no longer appear highlighted or empty). 7. Complete all remaining required fields: topic, target URL, word count, and any additional options. 8. Review every field one final time to confirm nothing is blank. 9. Click Submit or Order only after all fields are confirmed — do not save as a draft again until the Content Type is locked in. ⚠️ Important Things to Avoid - Do not refresh the page while filling out a new press release draft — this resets field selections. - Do not navigate away from the draft form before all required fields are complete. - Do not try to fix the original broken draft by re-selecting the category. The internal validation error is tied to the saved state and will not resolve without deleting and recreating the draft. 🧩 Still Seeing the Error After Recreating the Draft? If the error persists after following the steps above, check the following: - Confirm the Content Type dropdown shows a visible, non-placeholder selection (e.g., Press Release, not Select a type…). - Ensure you are working inside the correct OTTO project — submitting from a different project context can cause field mismatches. - Try clearing your browser cache or using a different browser to rule out a cached form state. 💬 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 a USAToday Press Release Nofollow Link Issue

🔍 Overview If your press release distributed through Search Atlas was published on USAToday with a nofollow link instead of a dofollow link, this article explains what happens next and what you can expect from the resolution process. Important: Search Atlas cannot directly edit or delete content published on USAToday. Changes must be requested through the publisher, which our team handles on your behalf. ⚠️ Why This Happens - USAToday and other third-party publishers control how links are tagged on their platforms. In some cases, a press release may be published with a nofollow attribute even when a dofollow link was expected. - This issue originates at the publisher level and cannot be corrected by editing the press release inside the Search Atlas platform after publication. 🛠️ What Search Atlas Does to Resolve It 1. Contacts the publisher directly. Our team reaches out to USAToday to request a correction or removal of the affected press release. 2. Confirms the outcome. Once the publisher has acted — whether that means correcting the link attribute or removing the press release — our team will update you on the result. 💡 How to Get This Resolved To initiate the correction process, follow these steps: 1. Locate the URL of the published press release on USAToday. 2. Confirm the link in question is tagged as nofollow when it should be dofollow. 3. Decide whether you want the press release corrected (link attribute fixed) or removed entirely from USAToday. 4. Contact our support team and provide: the USAToday press release URL, confirmation that the issue is a nofollow link, and your preferred resolution (correction or removal). 5. Our support team will immediately contact USAToday on your behalf to request the appropriate action — no further information will be needed from you if you include the details above. Submitting complete details in your first message allows our team to contact the publisher right away without additional back-and-forth. 📊 What to Expect After Reporting - Action: Our team will contact USAToday to request that the press release is corrected or removed, depending on your preference. - Confirmation: Our team will follow up with you once USAToday has acted on the request. If you have any questions about the status of your request, please contact our support team and we will be happy to help.

🛠️ Signal Genesys: Fixing an Invalid Publish Date Error on Press Releases

Overview If you receive an "Invalid publish date" error when trying to publish a press release in Signal Genesys, the date entered in the publish date field is either incorrectly formatted, set in the past, or missing entirely. This article shows you where to find the publish date field and how to correct it to resolve the error. What the Error Means Signal Genesys validates the publish date before submitting a press release to distribution partners. The invalid publish date error appears when: - The date is set in the past — press releases must be scheduled for today or a future date and time. - The date format does not match the expected format for your region. - The publish date field was left blank. - A previously scheduled release was never published and its scheduled date has now passed. Where to Find the Publish Date Field 1. Open the press release you want to publish inside Signal Genesys. 2. In the press release editor, look for the Article Details, Distribution Settings, or Settings panel — this is typically located in the right-hand sidebar or at the top of the editing form. 3. Locate the field labeled Publish Date or Publication Date. 4. Click the field to open the date and time picker. Note: If you do not see the Publish Date field immediately, scroll down within the settings panel — it may appear below other metadata fields such as Category or Tags. How to Fix the Invalid Publish Date Error 1. Click the Publish Date field to open the date picker. 2. Select today's date or any future date. 3. If a time field is also present, ensure the time is set to a future time when using today's date. 4. Click Save, Update, or Apply to confirm the change within the editor. 5. Attempt to publish the press release again — the error should no longer appear. Additional Tips - If the date picker does not accept your input, try typing the date manually using the format shown in the placeholder text (commonly MM/DD/YYYY or YYYY-MM-DD). - Ensure your browser's timezone matches your intended publish timezone — Signal Genesys evaluates dates against server time. - If the publish date field appears greyed out or read-only, the press release may be in a locked or processing state. Cancel the current submission attempt, return to the draft, update the date, and resubmit. - For releases stuck in a Pending state with an expired date, create a new draft rather than attempting to republish the old entry. Still Getting the Error? If you have set a valid future date and the error persists, contact Search Atlas Support via the in-app Help Widget. Provide the title of the press release, the date and time you are trying to set, and a screenshot of the error message if possible. Related Articles - Signal Genesys (Press Release Distribution & GBP Deployment) - Search Atlas — Signal Genesys (Press & PR) Issues - Create a Press Release in Search Atlas - Core Components of a Press Release: Structure and Formatting Guide

Embed Your Signal Genesys Press Releases on Your Website

📌 Overview Signal Genesys lets you publish press releases and display them directly on your website using an embed code snippet. This article shows you exactly where to find that snippet inside app.signalgenesys.io and how to paste it into your site. 🔍 Where to Find the Embed Code in Signal Genesys 1. Log in to your account at app.signalgenesys.io. 2. In the left-hand navigation, click Media Room. 3. Look for the embed or code snippet option within the Media Room section. The exact label or button may vary — if you are unsure where to locate it, contact our support team and we can guide you directly to the correct spot in your account. 4. Once you have located the embed option, copy the full block of HTML or JavaScript code it provides. That copied code is your embed snippet. It tells your website to pull and display all press releases from your Signal Genesys Media Room automatically. 🌐 How to Add the Embed Code to Your Website The steps below cover the most common website types. The process is the same regardless of platform — you are pasting a block of code into a page. - WordPress: Open the page or post where you want press releases to appear. Switch the editor to Code editor (or add a Custom HTML block), then paste the snippet. Publish or update the page. - Wix / Squarespace / Webflow: Add an Embed or Custom Code element to the page, paste the snippet inside it, and save. - Raw HTML site: Open the relevant .html file, paste the snippet where you want the press release list to appear (between the <body> tags), and save the file. Once the page is published and refreshed in a browser, your press releases should render in that location automatically. ✅ Confirming the Embed Is Working 1. Visit the page on your live website in a new browser tab. 2. You should see your press releases listed exactly as they appear in your Signal Genesys Media Room. 3. If nothing appears, hard-refresh the page (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) to bypass any browser cache. 4. Make sure the snippet was pasted in full — partial code will not render correctly. Return to app.signalgenesys.io and copy it again if needed. ⚠️ Common Issues and Quick Fixes - The embed area is blank: Confirm you have at least one published press release inside Signal Genesys. Drafts will not display. - Code appears as plain text on the page: The snippet was pasted into a visual text field instead of an HTML/code field. Switch to the code or custom HTML view and paste it there. - Still not loading after following these steps: Reach out to our support team through the chat icon on this page and we will help you resolve it directly.

Premium Press Release Distribution Channels in Search Atlas

Overview Search Atlas has expanded its PR distribution network to include additional high-authority media outlets. These premium channels give users access to more visibility, stronger backlinks, and greater brand credibility through some of the most trusted publications available. Available Premium Distribution Channels USA Today One of the most trusted and widely read publications in the United States. USA Today offers massive reach and brand recognition, making it ideal for campaigns where visibility and credibility are top priorities. MarketWatch A leading financial news outlet with millions of monthly readers and strong organic reach. MarketWatch is especially valuable for finance, business, and investment-related press releases that benefit from a financially engaged audience. AP News A global news authority with unmatched syndication power. AP News placements are intended for brand credibility, trust signaling, and client-facing validation. Note that AP News distributions are no-index, so they are not designed to drive SEO or AI citation impact directly. DA80 Network A premium aggregated channel that distributes your content across 20+ outlets with an average Domain Authority of 80+ from a single submission. This provides efficient, high-authority coverage from one streamlined submission. Why These Channels Matter - Increased visibility: Reach audiences across some of the largest publications online. - High-authority backlinks: Earn links from domains with strong authority signals. - Brand trust: Boost credibility through placements on recognized media outlets. - No added complexity: Premium channels are integrated directly into the standard PR distribution workflow. Choosing the Right Premium Channel When selecting premium channels, consider your campaign's primary goal: - For SEO and AI visibility, choose indexed, do-follow channels such as USA Today and MarketWatch. - For brand credibility and trust signaling, AP News is ideal even though it is no-index. - For broad authority coverage, the DA80 Network distributes to 20+ high-DA outlets at once. Review the inline metrics shown during channel selection — including authority tier, estimated traffic, audience focus, and publishing time — to make informed decisions aligned with your campaign goals.

📍 Press Release Geographic Targeting: What's Available and How to Target Local Markets

🌎 Is geographic or state-level targeting available? Not as a direct targeting filter. Search Atlas Press Release distribution does not currently offer a state-level geographic filter where you select specific states or regions before distributing. 🏙️ How to target local and regional markets The best option for geographic targeting is the Local XPR channel: - Local XPR distributes to a curated network of local and regional news outlets across the United States - Coverage focuses on community newspapers, city news sites, and regional publications - It is the closest available option to geographic targeting within Search Atlas PR 🎯 Other options for geographic relevance - Include location in the press release content — mentioning the city, state, or region in the headline and body helps local outlets pick it up. In Step 1 of the press release flow, the address is auto-filled from your saved Locations data, so keeping the correct Location selected ensures the intended city and region appear in your release - Google Business Profile posts — for hyper-local announcements, GBP posts reach local search audiences directly

⚠️ Press Release Preview Appears Empty After AI Generation

If the Edit & Review panel (Step 3) in the press release creation flow appears blank immediately after using 'Generate with AI,' your content has been successfully generated and saved. This is a display issue only — a full page reload restores the preview instantly. 🔍 What's Happening After clicking 'Generate with AI' on Step 2 and advancing to Step 3 (Edit & Review), the preview panel may render as completely blank. AI generation completed successfully and your content is stored — only the visual rendering of the preview is affected. This issue can occur on any browser or operating system. 🛠️ Workaround Steps Follow these steps to restore your AI-generated content without losing any work: 1. After reaching Step 3 and seeing the empty preview, keep your browser tab open — do not close it. 2. Perform a full page reload: press F5 on Windows or Linux, or press Cmd+R on Mac. 3. Navigate back to the press release you were editing. 4. Your AI-generated content will now appear correctly in the preview panel. Your content was saved during generation — the blank preview is a rendering issue only, and the reload resolves it. 📡 Engineering Status Our engineering team has identified the root cause of this display issue. A fix has been released and is being rolled out to all users. Your data is safe and no generated content has been lost. If you are still experiencing the blank preview after reloading, your account may not yet have the fix deployed. 📞 When to Contact Support If the workaround does not restore your content after a full page reload, or if you cannot locate your press release after reloading, please contact Search Atlas Support. Include your press release ID and details such as when you generated the content and which browser you're using so our team can investigate quickly. Avoid closing your browser tab during troubleshooting, as this may affect our ability to assist you. 🎯 A permanent fix for this preview rendering issue has been released and is being rolled out. Your AI-generated content is always saved. If you are still seeing a blank preview after reload, your product may not yet have the fix deployed — contact Support with your press release ID and we'll investigate.

🖼️ Supported Image Formats for Press Releases

Press release images must be in a supported format before you publish. Uploading a WEBP, AVIF, or HEIC file triggers a validation error at the Step 3 preview — convert your image first to avoid a blocked submission. ✅ Accepted Image Formats Search Atlas accepts the following formats for press release image uploads: - JPEG / JPG — recommended for photos and product images - PNG — recommended for logos and graphics that require transparency - GIF — supported for static or animated images If your file is saved as .jpg, .jpeg, .png, or .gif in its true native format, it will pass validation and upload successfully. 🚫 Blocked Formats: WEBP, AVIF, and HEIC The following formats are not accepted and will be blocked at Step 3 (Preview) before your press release reaches the distribution network: - WEBP — a modern web format not supported by all press release distribution systems - AVIF — a next-generation image format not compatible with the distribution network - HEIC — the default photo format on Apple devices (iPhone, iPad, and Mac) These formats are blocked to prevent broken or black-background images from appearing in your published press release. The validation check runs at Step 3, so your draft is saved when the error appears. Go back to Step 2 to replace the flagged image without losing any other press release content, then return to Step 3 to re-run the preview. ⚠️ Mislabeled File Extensions A file renamed to .jpg or .png but originally saved as WEBP, AVIF, or HEIC will also fail validation. The format check reads the actual file data — not just the file name — so renaming the extension alone does not fix the error. Re-export or convert the image to a truly supported format using the steps below. 🔄 How to Convert an Unsupported Image to JPEG or PNG Use any of the methods below to convert your image before uploading to your press release. On Windows 1. Open the image in Paint or Photos. 2. Select File → Save as. 3. Choose JPEG picture or PNG picture from the file-type menu. 4. Save the file, then upload the converted version to your press release. On Mac 1. Open the image in Preview. 2. Select File → Export. 3. Choose JPEG or PNG from the Format dropdown. 4. Click Save, then upload the exported file to your press release. Using a Free Online Tool 1. Go to a free converter such as Squoosh or Convertio. 2. Upload your WEBP, AVIF, or HEIC file. 3. Select JPEG or PNG as the output format. 4. Download the converted file. After converting, return to your press release draft, replace the flagged image with the new file, and proceed to Step 3. The validation check will pass and you can submit for distribution. 🎯 You now know that Search Atlas press releases accept JPEG, PNG, and GIF images only — and that WEBP, AVIF, and HEIC files (including files merely renamed to .jpg or .png) will be blocked at the preview step. Convert any unsupported file using the steps above, then re-upload to publish without errors. For more help building and distributing press releases, see the Press Release Creation Guide.

📰 US Today Publication Status After Cancellation

📰 What happens after cancellation? Cancelling your Search Atlas subscription does not automatically provide a publication status update. Publication work may already be in progress, so the status must be checked against the specific customer and order. 🔎 How to request an update 1. Open the chat widget in the bottom-right corner of the Search Atlas platform. 2. Type human teammate to connect with our team. 3. Provide the customer’s name, account email, and any available publication or order details. 4. Ask for the current status of the US Today publication. 📋 Information we can verify Our team can review the available order records and confirm whether the publication is pending, in progress, completed, or requires additional information. Updates depend on the publication’s current stage and the records associated with the account. ⚠️ If the customer no longer has access A cancelled subscription may limit access to Search Atlas features and historical order information. The customer or an authorised account representative can still request a status review through the chat widget using the account details associated with the publication. 💬 Need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.