Troubleshooting: Link Lab & Publisher Orders
By Camilo Aponte
By Camilo Aponte
π Link Laboratory Publisher Auto-Assign & HDC Refund Issues
Overview Some customers have encountered a situation in Link Laboratory where a publication is rejected but no alternative publisher can be selected β the selection page loads blank with nothing actionable. In some cases, the platform then auto-assigns the order to a publisher without consent. This article explains what is happening and exactly what to do if you are affected. β What Causes This Issue These problems are related to the publisher assignment flow in Link Laboratory and can involve: - The publisher selection page appearing blank when a replacement is needed after a rejection. - An order being automatically reassigned to another publisher without your approval. - Orders remaining in an unclear state with no path to select a new publisher. How to Resolve Affected Orders If your Link Laboratory orders are affected by auto-assign issues, a blank publisher selection page, or incorrect publisher assignments, follow these steps to prepare your request and understand what the support team will do on your behalf: 1. Identify the affected orders. Note all Link Laboratory order numbers where a publication was rejected, auto-assigned without your approval, or where you were unable to select a replacement publisher. Having these order numbers ready will speed up resolution. 2. Contact the Link Laboratory Exchange support team and provide your list of affected order numbers. In your message, specify which of the following actions you need: - Disable auto-assign for your account, so no further orders are reassigned to a publisher without your explicit approval. - Cancel incorrectly assigned orders for any orders that were auto-assigned to a publisher you did not approve. - Process an HDC credit refund for each cancelled order, returning the HDC credits to your account balance. - Manually assign a replacement publisher for any links that still need to be placed after the affected orders are resolved. 3. Confirm the changes with the support agent. Once the team has acted on your request, verify that auto-assign is turned off on your account, that the cancelled orders no longer appear as active, and that your HDC credit balance reflects the refunded amounts. 4. Place new orders manually. After your account is corrected, you can return to Link Laboratory and manually select your preferred publisher when placing or replacing orders, ensuring you retain full control over publisher assignments going forward. If you are unsure which orders are affected or need help identifying them, the support team can review your account and flag impacted orders for you. β Contact Support Because disabling auto-assign, processing HDC credit refunds, and cancelling incorrectly assigned orders require action from the Link Laboratory Exchange team, please reach out to our support team so an agent can review your account and apply these corrections as quickly as possible. You can contact us by visiting the Search Atlas Help Center and starting a conversation with our team.
π Fix and Replace a Misplaced Publisher Backlink
π Overview If your article was published on a site that does not match your niche or campaign goals, you can request a publisher replacement through the Link Lab feature inside Search Atlas. This article explains how to identify the issue and what to do next. π When Should You Request a Replacement? You should request a publisher replacement if any of the following apply: - Your article was placed on a site that is irrelevant to your industry or target audience. - The publisher site does not meet the quality or niche criteria you specified at the time of order. - You have not received an update on your placement and want to escalate the request. π οΈ How to Submit a Publisher Replacement Request Because publisher replacements and urgent link building requests require direct coordination with our team, there is no fully self-serve flow to complete a replacement on your own. To get this resolved, you will need to contact our support team directly (see below). When you do, have the following information ready so we can process your request as quickly as possible: - Campaign name and order ID β found inside your Link Lab campaign details. - Current publisher URL β the site where the article was incorrectly placed. - Preferred replacement publishers β any alternative sites you would like us to consider, along with your niche or targeting criteria. - Replacement article β a new or revised article ready to share with our team if a new publisher is identified. - Urgency or deadline β let us know if this is a time-sensitive request so our team can prioritize accordingly. β±οΈ What Happens After You Reach Out Once our team receives your replacement request, they will review the details and coordinate directly with you on next steps, including identifying a suitable replacement publisher and confirming placement. Our team will keep you updated throughout the process. 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.
π° Publisher Payment Pricing Discrepancies
π Why prices may differ The price shown for a publisher can change depending on when and where you view it. Search Atlas may display a current publisher rate, while a published article can retain a different price captured at checkout, assignment, or placement. For example, a publisher may currently show $147 even though an earlier offer was $200. A rate may also appear much lower after publication if you are viewing the publisherβs live catalog price instead of the cost saved for your order. π³ Which price applies to payment The amount used for publisher payment is the cost attached to the specific order or placement recordβnot necessarily the publisherβs current catalog price. Depending on the workflow, this amount may be captured when the publisher is assigned, when checkout is completed, or when the article is posted. Do not use a live publisher listing to calculate the payout for an existing placement. The listing may be repriced for future orders while the completed order remains associated with its saved cost. β What to check first 1. Open the relevant order or published article in Search Atlas. 2. Confirm the publisher domain, article URL, and number of placements. 3. Review the order line, assignment details, checkout record, or payout information for the saved cost. 4. Compare the saved cost with the original agreement or approved order amount. 5. Check whether the amount shown is the publisher cost, your customer-facing price, or a current marketplace price. π οΈ When to request a review Request a review when the saved cost for the placement does not match the approved order terms, or when a completed placement appears to have been overwritten with a newer live publisher price. Include the publisher domain, article URL, order or placement ID, agreed amount, displayed amount, and screenshots showing the discrepancy. A lower current publisher price alone does not confirm a payout error. It may apply only to new orders and may not change the cost already recorded for your published article. π© How to 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.
π Handle Publisher Mismatch and Order Refunds
π Overview When a publisher is unable to fulfill your Link Lab order, Search Atlas may offer replacement publisher options. Occasionally, none of the suggested replacements may align with your target country or niche. This article explains what to provide when requesting help with a publisher mismatch and order refund. π Publisher Replacement Mismatch If the replacement publishers offered for your order do not meet your niche or country requirements, do not accept a mismatched option. Gather the affected order number, the original publisher, the replacement options offered, and the specific reasons they are not suitable. β οΈ Requesting Help With the Order 1. Review the replacement options. Confirm which publisher requirements are not met, such as the target country or niche. 2. Keep the order details ready. Include the order number, original publisher, replacement options, and a clear explanation of the mismatch. 3. Contact support. Ask the team to review the mismatch and your refund request. π° Order Refunds If the offered replacement publishers do not meet your requirements, contact support with the order details and explain that you are requesting a refund because of the mismatch. The team can review the order and advise you on the available resolution. π οΈ Information to Provide - The affected Link Lab order number - The original publisher - The replacement publisher options offered - The niche or country requirements that were not met - Your request for an order refund 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 Publisher Mismatch and Order Refunds
π What Is a Publisher Replacement Mismatch? A publisher replacement mismatch occurs when a replacement publisher does not meet the requirements of your original order. β What You Should Do 1. Review the replacement publisher against your original order requirements. 2. If the replacement does not meet those requirements, do not accept it. 3. Contact support to report the mismatch and request a refund for the affected order. π° What to Include in Your Request Have the affected order details ready and explain how the replacement publisher differs from your original requirements. Our team can review the mismatch and advise on the refund. 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.
π§ Managing Outreach Campaigns and Frozen Account Billing
π Overview This article covers two related topics that customers often ask about together: removing outreach campaigns in the Authority section and understanding whether a frozen or inactive account still incurs charges. Read on for a clear explanation of both. π Where to Find Outreach Campaigns Outreach campaigns are managed inside the Authority section of the platform. To navigate there: 1. Click Authority in the left sidebar. 2. Select Campaigns from the sub-menu. From this page you can view all active and draft outreach campaigns associated with your account. π οΈ Known Issue: Unable to Delete Outreach Campaigns We are aware of a bug that currently prevents some customers from deleting outreach campaigns. This issue has been identified and logged by our engineering team and a fix is awaiting release. Until the fix is deployed, here is what you can do: - Pause the campaign to stop any further outreach activity while the bug is resolved. - Note the campaign name and contact our support team via the chat widget so we can manually action the deletion on your behalf if needed. - Check back for platform updates β the fix will be rolled out automatically and no action will be required from you once it is live. We apologise for the inconvenience and appreciate your patience while our team resolves this. π³ Billing for Frozen or Inactive Accounts A common follow-up question is whether charges continue when an account is frozen or when campaigns are not actively running. Here is how billing works: - Subscription charges are based on your active plan, not on the number of campaigns running. If your account is on a paid plan, billing continues regardless of whether campaigns are paused or inactive. - A frozen account typically refers to an account where functionality has been restricted β for example, due to a disconnected email or a payment issue. In most cases, your subscription billing cycle continues during this period. - To avoid charges, you would need to downgrade or cancel your subscription through your account settings before your next billing date. If you are unsure whether your specific account is being charged during a frozen state, our support team can review your billing details and confirm the exact status. β Steps to Pause or Manage an Outreach Campaign While the delete function is temporarily unavailable, follow these steps to stop an outreach campaign from sending: 1. Go to Authority in the left sidebar. 2. Click Campaigns. 3. Locate the campaign you want to stop. 4. Open the campaign and look for the option to pause or disable it. 5. Confirm the change. The campaign will stop sending outreach emails immediately. Pausing a campaign ensures no further emails are sent while you wait for the delete functionality to be restored. π Connected Email Accounts Outreach campaigns rely on a connected email account to send messages. If your email account becomes disconnected, campaigns linked to that account will not send. However, the campaign itself will remain in your list until it is deleted. To reconnect your email or manage linked accounts, go to Authority β Inbox and review your connected accounts from there. π¬ 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.
π Link Lab Replace-Publisher Option Not Appearing
π Overview If you received an email asking you to select a replacement publisher for a Link Lab order, but the option to change publishers is not visible or functional inside the platform, you are not alone. This was a confirmed platform issue affecting existing orders. The engineering team has since resolved the underlying bug. This article explains what happened, what to expect, and how to get help if the issue persists for your order. βοΈ What Caused This Issue A bug in the Link Lab system caused the replace-publisher option to be missing on certain existing orders even when customers were actively prompted by email to take action. In some cases, the order status was incorrectly pinned to a rejected state while still holding an open publisher assignment, which prevented the replacement flow from appearing correctly. An additional issue caused the alternative-publisher selection to fail entirely when a publisher re-engaged after a prior rejection. Both bugs have been fixed by the engineering team. β What Was Done to Resolve Affected Orders For orders where this issue was confirmed, the Search Atlas Link Lab team manually reviewed each affected order and progressed them through the publisher-assignment process. Completed orders were marked as done, and orders still in progress were handled by the team directly without requiring further action from the customer. π οΈ What To Do If You Are Seeing This Right Now If you received an email to select a new publisher but the replace-publisher option is still not available in your order, follow these steps: 1. Check your order status. Log in to the platform and navigate to your Link Lab orders to review the current status of the affected order. If the order already shows as completed, no further action is needed on your part. 2. Check your inbox and spam folder. A follow-up email may have been sent confirming the order was completed or providing updated instructions. 3. Wait briefly if the order is in progress. If the order status shows it is still being processed, the Link Lab team may already be handling it. Allow some time before escalating. 4. Contact support if the issue persists. If the replace-publisher option is still missing and your order has not progressed, reach out to the support team immediately using the steps below. π‘ What To Include When Contacting Support To help the team resolve your issue as quickly as possible, have the following information ready before you open a chat: - Your Link Lab order number(s) (e.g. the numeric ID shown in your order list or in the email you received) - The email subject or date of the message prompting you to select a new publisher - A brief description of what you see β or do not see β when you navigate to the order π Get Support 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 a Link Laboratory Order Issue
π Overview Link Laboratory is the link-building order center inside Search Atlas. If your order appears stuck, unconfirmed, or is not progressing as expected, this article explains what to do and how to escalate effectively so the support team can resolve your issue as quickly as possible. β οΈ Common Order Problems - Order shows no status update: Orders can take time to move through the fulfilment pipeline. Allow up to the estimated timeframe shown on your order before escalating. - Order appears stuck or pending: This may indicate a technical issue that requires investigation by the Search Atlas team. - Order not visible in your dashboard: Confirm you are viewing the correct workspace. If you manage multiple projects, switch to the relevant project from within the platform. - Unexpected order status change: Check any in-platform notifications or messages associated with your account for any related communications. π οΈ How to Escalate a Link Laboratory Order Issue Because Link Laboratory order issues may involve backend processing that cannot be resolved through self-serve steps alone, the most effective path is to contact the support team directly. To help the team investigate and resolve your issue as quickly as possible, please have the following information ready before you reach out: - Your project or workspace name β the specific Search Atlas project the order is associated with. - The order details β including the target URL, anchor text, and any other details visible on the order. - A description of the problem β for example, what status the order is currently showing, how long it has been in that state, and any error messages you have seen (copied exactly as displayed). - The approximate date and time the issue was first noticed. - Any relevant screenshots β if you are able to capture the order view showing the unexpected status or missing information, this will speed up the investigation. Having these details ready when you contact support will allow the team to look into the backend status of your order without back-and-forth delays. π Before You Escalate β Quick Checks 1. Confirm you are in the correct workspace: If you manage multiple projects, make sure you are viewing the project where the order was placed. 2. Check for in-platform notifications or messages: Your account may have received a communication from the Search Atlas team regarding an action required on your order. 3. Verify your billing information is current: If payment did not complete, the order may not have entered the fulfilment queue. Check your account settings to confirm your billing details are up to date. 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.
π« Handling Unsolicited Pitches and Spam Outreach
π What Is This About? Some Search Atlas users have reported receiving unsolicited messages through the platform β typically SEO service offers, link-building pitches, or business proposals that include sample websites and requests for a reply. These messages are not sent or endorsed by Search Atlas and are considered spam or unsolicited solicitation. This article explains what to do if you receive one of these messages and how to keep your inbox clean. π¬ Where These Messages May Appear Unsolicited pitches can arrive through the outreach-related sections of the platform. If you receive a message you did not request or notice activity you did not initiate, check your outreach and messaging areas within the platform and take action immediately using the steps below. β οΈ How to Recognise an Unsolicited Pitch Unsolicited solicitations typically share these characteristics: - Offers of SEO, link-building, or guest posting services you never requested - Lists of sample websites or client references included in the message body - Requests to reply to a proposal or click an external link - Sender details you do not recognise or that seem unrelated to your projects - A generic greeting with no reference to your specific business or domain If a message matches any of these patterns, treat it as unsolicited and do not reply, click any links, or share personal or payment details. π οΈ What to Do If You Receive One 1. Do not reply β responding confirms your address is active and may invite more solicitations. 2. Do not click any links β external links in unsolicited messages can pose security risks. 3. Note the sender details β take a screenshot or copy the sender name and message content before taking further action. 4. Delete or dismiss the message β remove it from your outreach inbox to keep your workspace tidy. 5. Report it to our team β open the chat widget (see below) and share the sender details so we can investigate and take appropriate action. π Protecting Your Account Search Atlas does not facilitate or endorse third-party solicitation within the platform. To reduce exposure: - Regularly review your outreach inbox for any unexpected messages. - Ensure only trusted team members have access to your workspace β manage access via your account settings. - If you suspect your account credentials have been compromised, change your password immediately. 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 Outreach Inbox Unread Count No Messages
Overview If your Outreach inbox displays an unread message count but shows no content when you open it, or if your emails are taking longer than expected to sync, this article explains the most common causes and the steps you can take to resolve them. This issue affects the Inbox section inside the Digital PR and Outreach tools. Common Causes of the Unread Count Display Bug Seeing an unread badge without any visible messages is usually caused by one of the following: - Email sync still in progress: Messages have been detected by the system but have not yet fully loaded into the inbox view. - Incomplete email account connection: The connected email account lost its authentication or was disconnected mid-sync, leaving ghost counts behind. - Browser cache conflict: Outdated cached data in your browser can cause the inbox UI to display stale or mismatched information. - Filter or folder mismatch: Active inbox filters may be hiding messages that the unread counter is still tracking. Common Causes of Email Sync Delays Email syncing in the Digital PR and Outreach modules depends on a live connection between Search Atlas and your linked email provider. Delays can occur when: - Your email provider is experiencing service issues or rate limiting. - The OAuth token for your connected account has expired and needs to be re-authenticated. - A large volume of emails is being synced for the first time after a new account connection. - Your inbox has a high number of messages or threads, which increases initial sync time. - Network interruptions occurred during an active sync cycle. Initial syncs for newly connected accounts may take some time depending on mailbox size. Subsequent syncs are typically faster. Step-by-Step Troubleshooting Follow these steps in order to diagnose and resolve the issue. 1. Wait and refresh: If you recently connected your email account or sent a campaign, wait a few minutes and then hard-refresh the page using your browser's refresh shortcut. 2. Clear your browser cache: Go to your browser settings, clear cached images and files, then reload the platform. 3. Check your inbox filters: Navigate to your Outreach or Digital PR inbox and confirm that no active filters are narrowing the view. Reset any applied filters to show all messages. 4. Reconnect your email account: If messages are still missing, disconnect your email account from the platform's email connection settings and reconnect it. This forces a fresh authentication and a new sync cycle. 5. Try a different browser or incognito mode: If the issue persists after clearing cache, open the platform in a private/incognito window or a different browser to rule out a local browser conflict. 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 Outreach Campaign Schedule Error
π What This Error Means When you see the message 'Please configure outreach schedule first!', it means your outreach campaign is missing a required sending schedule. Search Atlas will not allow a campaign to launch until a valid schedule is set. This is a quick fix β follow the steps below to resolve it. π οΈ How to Configure Your Outreach Schedule 1. In the left sidebar, open your outreach campaigns list. 2. Locate the campaign showing the error and click on it to open the campaign settings. 3. Navigate to the Schedule section within the campaign editor. 4. Set your preferred sending days, time window, and time zone. All three fields are required before you can proceed. 5. Click Save to confirm your schedule settings. 6. Return to the campaign overview and attempt to launch your campaign again. β Tips for a Valid Schedule - Select at least one sending day β campaigns with no active days cannot be scheduled. - Set a valid time window β your start time must come before your end time. - Choose a time zone β leaving the time zone blank will trigger the same error even if other fields are filled in. - Save before launching β always save your schedule changes before clicking the launch button. π Launching Your Campaign After Setup Once your schedule is saved, the error should no longer appear. Go back to your campaign in your campaigns list, confirm the schedule is displayed correctly in the campaign summary, then click Launch. Your campaign will begin sending according to the schedule you configured. π‘ Still Seeing the Error? If you have completed all the steps above and the error persists, it is possible that the schedule did not save correctly due to a browser or session issue. Try the following: - Refresh the page and re-enter your schedule settings before saving again. - Clear your browser cache or switch to a different browser. - Check that no required fields are highlighted in red, which indicates an incomplete entry. If the issue continues after trying these steps, 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.
π οΈ Troubleshooting Bulk Campaign Emails Not Sending
This article explains why selecting contacts for a bulk campaign send may result in only a small number of emails actually going out β and what to do about it. π What's Happening When triggering a bulk send in a campaign, it is possible for the action to appear to complete while only a fraction of the selected emails are actually dispatched. This is a known issue that our team can investigate and resolve on your behalf. π οΈ What to Do 1. Note the name of the affected campaign and, if possible, the approximate number of contacts you selected versus how many emails were actually sent. 2. Note the date and time (including your timezone) when you triggered the bulk send. 3. Reach out to our support team using the contact method described below and provide these details so we can investigate your account and get your emails sending correctly. β What to Have Ready When You Contact Us - The name of the affected campaign - The number of contacts selected for the bulk send - The number of emails that actually went out - The date and time the bulk send was triggered 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.
π Troubleshooting Campaign Bulk Emails Not Sending
This article explains what to do when you trigger a bulk email send from a campaign and only a few emails go out β or none at all. Use the diagnostic steps below to rule out common causes before escalating to our support team. π What This Issue Looks Like You select one or more contacts in a campaign and trigger a bulk send action. The trigger appears to complete, but little or no email activity follows β contacts remain in their pre-send state and no outreach is logged. π οΈ Self-Serve Checks to Try First 1. Verify campaign status. Open the campaign and confirm it is set to Active. If the campaign is paused or in draft mode, bulk sends will not go out even after you trigger them. 2. Check your contact filters. Review the contact list or segment you selected. If filters are set too narrowly β for example, excluding contacts who have already received an email β your eligible contact count may be zero or near zero, which would explain minimal send activity. 3. Review your account's send limits. Some plans have daily or monthly outreach limits. Navigate to your account or billing settings and confirm you have not exhausted your send quota for the current period. 4. Check contact email validity. If the contacts you selected have unverified, bounced, or opted-out email addresses, those sends will be silently skipped. Review the contact records for any deliverability flags. 5. Re-trigger a small test batch. Select two or three contacts whose email addresses you can verify and trigger a send manually. If those go through, the issue may be isolated to a specific segment or filter condition rather than a platform-wide problem. 6. Check for recent account or permission changes. If your role or team permissions were changed recently, your account may no longer have the access level required to execute bulk sends. Confirm with your workspace admin that your permissions are intact. πΊ If the Issue Persists β What to Prepare Before Escalating If none of the above steps resolve the issue, our support team will need to review your backend send logs. Please have the following ready when you reach out: - The exact name of the campaign where the bulk send stalled - Approximately how many contacts you selected and when you triggered the send (date, time, and your timezone) - A screenshot or description of any confirmation message, error message, or lack of response you saw immediately after triggering the send - Whether the issue is consistent with one campaign or occurs across multiple campaigns - Your current plan or subscription tier, and whether any account changes were made recently β What to Expect Once you escalate with the details above, our team can review the backend send logs for your account and determine why the bulk send did not complete as expected. 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 Site Catalog Access Issues for Publisher Placement
π Overview The Site Catalog allows you to browse publisher sites and switch your placement to a different niche β for example, moving from a general category to a garage door-related niche. If you are unable to open the Site Catalog or switch your publisher placement, an access issue may be preventing you from doing so. This article explains what to expect and how to escalate so the Search Atlas team can resolve it on the back end. β οΈ Common Reasons for Site Catalog Access Issues - Insufficient account permissions: Your user role may not have the access level required to view or modify publisher placements. - Subscription or plan restriction: Site Catalog access may be tied to a specific plan or add-on that is not currently active on your account. - Account configuration: In some cases, access must be enabled manually by the Search Atlas team on the back end. π οΈ What to Expect and How to Escalate Site Catalog access issues β including the inability to switch publisher placements to a specific niche such as garage door-related categories β are typically resolved by the Search Atlas team through a back-end configuration change. There is no self-serve fix available for this type of issue. When you contact support, please have the following information ready so the team can act quickly: - Your project name and the account email address associated with your Search Atlas account. - A description of the exact issue you are experiencing (e.g., unable to open Site Catalog, unable to switch publisher placement to a specific niche). - The niche or category you are trying to switch your placement to (e.g., garage door services). - Any error message displayed, along with the approximate date and time the issue first occurred. π‘ Tips to Avoid Future Access Issues - Ensure your account is configured with the appropriate permissions before attempting to switch publisher placements. - If you expect to switch niches regularly, confirm with the Search Atlas team that your account is set up to support that workflow. 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 Email Campaign Over-Sending and Bounces
π Overview If your email campaign delivered more messages than the number of contacts you selected β or if you noticed a high bounce rate β this article explains the most common causes and how to resolve them. π Why Did My Campaign Send More Emails Than Expected? There are several reasons a campaign may exceed your intended send count: - Duplicate contacts in your list: If the same email address appears more than once across your selected segments or contact lists, each instance may trigger a separate send. Deduplication does not always happen automatically if contacts were imported from multiple sources. - Multiple list segments selected: When you build an audience from more than one segment, contacts who belong to several segments can be included multiple times unless a unique-contact filter is applied before sending. - Retry logic on soft bounces: The platform automatically retries delivery for soft bounces (temporary delivery failures). Each retry counts as an additional send attempt in your campaign metrics, which can inflate the total send number shown in your report. - Transactional or trigger duplicates: If the campaign was connected to an automation routine, the routine may have re-enrolled contacts who met the trigger condition more than once. π Understanding Bounce Types Bounces fall into two categories, and each requires a different response: - Hard bounces: The email address is invalid, does not exist, or the recipient domain is blocking delivery permanently. These contacts should be removed from your list immediately to protect your sender reputation. - Soft bounces: A temporary issue prevented delivery β for example, a full inbox or a server timeout. The platform retries these automatically. If a contact soft-bounces repeatedly, it will eventually be treated as a hard bounce. π οΈ How to Audit and Fix Your Contact List 1. Open the affected campaign from your email campaigns list. 2. Review the delivery report to identify the total send count, bounce count, and bounce type breakdown. 3. Export your contact list and check for duplicate email addresses. Remove any duplicates before your next send. 4. If you used multiple segments, consolidate them into a single deduplicated list and re-upload it before creating a new campaign. 5. Hard-bounce contacts should be suppressed or deleted from your audience. Do not attempt to re-send to addresses that have hard-bounced. β Best Practices to Prevent Over-Sending and High Bounces - Clean your list before every campaign: Remove invalid addresses, role-based addresses (e.g., info@, noreply@), and any contacts that have previously hard-bounced. - Use a single deduplicated segment: Merge all target contacts into one list and remove duplicates before selecting your audience in the campaign builder. - Verify new imports: When importing contacts from an external source, run a quick deduplication check and validate email format before saving the list. - Monitor your sender reputation: A bounce rate above 2% can damage your deliverability. Aim to keep hard bounces below 0.5% and soft bounces below 1.5%. - Review automation routines: If your campaign is triggered by a routine, open your automation routines and confirm that re-enrollment conditions are set correctly to avoid sending to the same contact multiple times. π‘ Checking Your Campaign Metrics You can review detailed send and bounce data for any campaign by going to your campaign analytics or reporting view. This view shows total sends, unique opens, bounce breakdowns, and unsubscribe counts. Use this data to identify patterns before launching future campaigns. π 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.
π° Guest Post Refunds: Stuck or Rejected Orders
π Understanding Refund Eligibility Guest post orders may qualify for refunds when placements are rejected by publishers or remain stuck in progress without resolution. Refunds are issued as HyperDrive credits (HDC) to your account balance. The system now includes automated refund actions for rejected placements, but some cases still require manual review by our team. π Checking Your Order Status Review the status of each placement in your guest post orders. Look for placements marked as rejected, stuck in pending review, or showing no progress after an extended period. The View Status table now includes a Refunded column to help you identify which placements have already been credited. π οΈ Using Self-Service Refund Options When a publisher rejects a placement, the Alternatives Drawer may appear with options to choose a replacement site or request an HDC refund. If you see a "Refund HDC" action, select it to trigger an automatic credit refund. For orders placed before this feature launched, or if the option does not appear, proceed to the next step. π¬ Reporting Stuck or Rejected Orders If your selection page from the email notification fails to load, or if you have orders with rejected or stalled placements that show no refund option, gather the order numbers and details of the affected placements. Include whether any placements went live successfully. π¬ Requesting Manual Review 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. Provide the order numbers and a summary of which placements were rejected or are stuck. Our team will verify each placement and process eligible refunds as non-recurring HyperDrive credits. π‘ Refund Details to Know Refunds are issued at the wholesale cost of the placement, not the retail price charged, so margins are not refunded. Credits are added as non-recurring HDC and can be used for future guest post orders. Once processed, the Refunded column in your order status will update to reflect the credit.
π Troubleshooting Common Link Lab Issues
π Overview Link Lab is Search Atlas's managed link-building tool that lets you place articles on publisher sites to earn high-quality backlinks. Like any complex workflow, occasional technical issues can arise β from orders missing article content to submission errors. This article walks you through the most common Link Lab problems and how to fix them. β οΈ Common Link Lab Issues and What They Mean Below are the most frequently reported issues in Link Lab and what typically causes them. - Order created but no article is shown for review: This can happen when an order is placed through the AI Agent and the article fails to attach correctly to the order record. The order exists, but the content is missing from the review screen. - Article submission not completing: The Content Genius to Link Lab bridge occasionally encounters errors when passing a drafted article into a Link Lab order. The article may appear complete in Content Genius but fail to transfer. - Missing "Replace Publisher" option: On some existing orders, the option to swap the publisher is not visible. This is a known issue that has been resolved for new orders, but older orders may still be affected. - Misleading post-completion guidance: After an order is marked complete, some users see edit prompts that no longer apply. This is a display issue and does not affect your order status. π οΈ Step-by-Step Troubleshooting Work through these steps before contacting support. Most issues can be resolved without escalation. 1. Refresh the order page. Navigate away from the order and return to it. Some display issues resolve with a fresh page load. 2. Check your order status. In Link Lab, locate your order and confirm its current status. If the status shows as complete but no article is visible, the content may not have transferred correctly. 3. Verify the article in Content Genius. Go to Left sidebar β Content β Content Genius and check whether the article was saved there. If the article exists in Content Genius but did not appear in your Link Lab order, this confirms a transfer issue. 4. Re-submit the article manually. If the article is available in Content Genius, try re-initiating the submission to Link Lab from within the article editor. Look for the Link Lab submission option in the article actions menu. 5. Check for browser or cache issues. Hard-refresh your browser (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) and try again. Try a different browser if the issue persists. 6. Note your order ID. If you still see a problem, make a note of your order ID (for example, a number such as 34611) before contacting support. This helps our team investigate quickly. π Information to Have Ready Before Contacting Support If the steps above do not resolve your issue, our support team will need the following details to investigate efficiently. - Your order ID or order number (visible on the order detail page) - The publisher name associated with the order, if known - A brief description of what you expected to happen versus what actually occurred - Any error messages displayed on screen (a screenshot is helpful) - Whether the order was created manually or via the AI Agent π‘ Tips to Avoid Link Lab Issues - Always review your article fully in Content Genius before submitting it to Link Lab. Incomplete drafts can cause transfer failures. - Avoid closing the browser tab immediately after placing an order. Wait for the confirmation screen to fully load. - If using the AI Agent to create Link Lab orders, double-check the order page shortly after the agent completes the task to confirm the article is attached. - For older orders missing the "Replace Publisher" option, create a new order with your preferred publisher rather than editing the existing one. π¬ Still Need Help? If you have followed the steps above and your Link Lab issue is not resolved, our 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.
π§ Fix Content Genius to Link Lab Bridge Failures
Overview After running a Guest Post Backlink campaign, some users are unable to push articles from Content Genius to Link Lab for publication. When this happens, the platform may report that the bridge between the two tools is blocked or unavailable. This is a known platform-level integration failure. Is This Happening to You? - You ran a Guest Post Backlink campaign in Link Lab. - You tried to push a completed article from Content Genius to Link Lab. - The platform returned an error indicating the bridge is blocked or unavailable. If this matches your situation, follow the self-service steps below before contacting support. What You Should Do 1. Refresh your session. Log out of Search Atlas completely, clear your browser cache, and log back in. Then navigate back to Content Genius and attempt the article push again. 2. Check the status of your Guest Post Backlink campaign in Link Lab. Open Link Lab, locate the campaign that was active when the error occurred, and confirm its status. If the campaign shows a pending, paused, or error state, wait for it to reach an active or completed state before retrying the push from Content Genius. 3. Retry the article push from Content Genius. Once your campaign status is confirmed as active or completed, return to Content Genius, open the article, and attempt to push it to Link Lab again. In many cases this resolves the bridge failure without further intervention. 4. Try pushing to a different or newly created Guest Post Backlink campaign. If the error persists on the original campaign, create a new Guest Post Backlink campaign in Link Lab and attempt to push the article to that campaign instead. 5. If none of the above steps resolve the issue, contact our support team. Take a screenshot of the exact error message and note the name of the campaign that was active when the error occurred. Share both with our team so they can investigate the integration failure at the account level and get your article submitted successfully. Background: What Causes This Issue A failure in the integration layer between Content Genius and Link Lab can prevent article submissions from going through when a Guest Post Backlink campaign is active. Campaign status conflicts or session-level issues are common triggers that can often be resolved by refreshing your session or targeting a different campaign. If the issue persists, it requires our support team to investigate on a per-account basis. Tips to Avoid Delays - Always record or screenshot any error message you see β exact error text helps our team pinpoint the cause faster. - Note the name of the Guest Post Backlink campaign that was active when the error appeared, as this helps our team identify the source of the conflict. Still Need Help? If you have followed the steps above and are still experiencing this issue, please reach out to our support team via the live chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team so we can investigate the bridge failure for your account and help you complete your article submission.
π§ Fix SMTP/IMAP Email Authentication Failures
π What Is This Error? When connecting your email account to Search Atlas, you may encounter an SMTP authentication failed error or an IMAP connection failure. This typically appears when linking a Google (Gmail or Google Workspace) account and prevents outgoing or incoming email from syncing correctly. This error is not caused by your browser cache or cookies. It is almost always related to account security settings or app permissions. Follow the steps below to attempt to resolve it. βοΈ Step 1: Check Your Google Account Security Settings Google has strict security controls that block connections from third-party apps using basic username and password authentication. To allow Search Atlas to connect, you need to verify the following: - Two-Factor Authentication (2FA): If 2FA is enabled on your Google account, you may need to use an App Password instead of your regular password (see Step 2). - Account permissions: Confirm the Google account you are connecting is the same one you use to sign in to Search Atlas. π Step 2: Generate a Google App Password An App Password is a 16-character code that can give Search Atlas secure access to your Google account without exposing your main password. To create one, navigate to your Google Account security settings, locate the 2-Step Verification section (you must have 2FA enabled), and look for the App passwords option. Follow Google's on-screen prompts to generate a password for use with Search Atlas. Once you have your App Password, return to your email connection settings in Search Atlas and re-enter your credentials using this App Password in place of your regular password. π Step 3: If the Issue Persists, Contact Support Because SMTP/IMAP authentication failures in Search Atlas can stem from account-specific configuration details that vary by setup, some cases require hands-on assistance from our team. Before reaching out, please have the following ready to help us resolve your issue as quickly as possible: - The exact error message you are seeing - The email address you are trying to connect - Whether your account uses standard Gmail or Google Workspace - Whether two-factor authentication (2FA) is enabled on the account - Any steps you have already tried 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 GMB Alerts and Reassign Rejected Guest Posts
π Overview This article covers two common questions: why you may not be receiving email alerts for Google Business Profile (GMB) post authorizations, and what happens to your guest post submission after a publisher in Link Laboratory rejects it. Both issues have straightforward solutions explained below. π¬ Why Am I Not Receiving GMB Email Alerts? Search Atlas sends email alerts when activity is detected on your Google Business Profile, including post authorization updates. If you are not receiving these emails, the most common reasons are: - Emails landing in spam or promotions: Check your spam, junk, and promotions folders. Add the Search Atlas sending address to your safe-senders list to prevent this going forward. - Alert threshold behavior: GMB alerts are triggered by any ranking position gain greater than zero on the Local SEO heatmap β including small movements such as a +0.1 position change. If you expected an alert for a larger movement only, be aware that the system is intentionally sensitive and will fire on any positive change. - Notification preferences not enabled: Confirm that email notifications are turned on for your account. Navigate to the top-right corner avatar, then review your profile and notification settings to ensure alerts are active. - Incorrect email address on file: Verify that the email address associated with your account is correct. Go to the top-right corner avatar β Settings β Profile (or Email Settings) to check your account email. If emails are reaching your inbox inconsistently, the most reliable fix is to whitelist Search Atlas in your email client and ensure your account email is up to date. π What Happens After a Publisher Rejects My Guest Post? When you submit a guest post through Link Laboratory (accessible via the top-right corner avatar β App Ecosystem β Publisher Exchange tab β Go to Link Laboratory) and the publisher rejects your placement, you are not left without options. Search Atlas has an automated reassignment system that works as follows: 1. Rejection is detected automatically: Once a publisher rejects your submission, the placement enters a 72-hour Pending Action window. During this window, you have the opportunity to take action or let the system handle it. 2. Daily auto-assigner runs: Every day, the auto-assigner reviews all publisher-rejected placements that are still within the 72-hour window and reassigns them to a suitable alternative publisher. 3. New placement is confirmed: Once reassigned, your guest post moves forward with the new publisher. You will be notified of the updated placement status. This means your campaign is not stalled by a single publisher's decision. The system automatically finds a replacement so your link-building timeline stays on track. β What Should I Do After a Rejection? While the auto-assigner handles most cases automatically, here are the steps we recommend: 1. Log in to Search Atlas and navigate to Link Laboratory via the top-right corner avatar β App Ecosystem β Publisher Exchange tab β Go to Link Laboratory. 2. Locate your rejected placement and check its current status in the dashboard. 3. If the placement is still within the 72-hour Pending Action window, you may also manually request reassignment or adjust your submission details before the auto-assigner runs. 4. After the window closes, confirm that a new publisher has been assigned and review the updated placement details. If the placement does not appear to have been reassigned after 72 hours, contact our team using the live chat widget for a manual review. π‘ Quick Tips to Avoid Future Issues - Keep your account email address up to date so you never miss an alert. - Whitelist Search Atlas emails to ensure delivery to your primary inbox. - Monitor Link Laboratory regularly during the 72-hour window after a submission, especially for time-sensitive campaigns. - Review your guest post content against publisher guidelines before submission to reduce the likelihood of rejection in the first place. π 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 Broken Links and Update URLs in Link Lab
π Overview Two common issues arise with Link Lab placements: needing to update the live URL for a published article, or finding that a publisher link has become broken or inaccessible. This article explains what each issue means and what information to have ready when you contact the team for hands-on help. π Understanding the Two Issues - Manual URL update: The article has been published, but the URL recorded in your Link Lab order needs to be changed β for example, because the publisher moved the post to a different address. - Broken publisher link: The URL associated with your placement is no longer accessible (returning a 404, redirecting incorrectly, or otherwise unreachable), meaning the backlink may not be passing value. π οΈ Requesting a Manual URL Update If the article is live at a different URL than the one recorded in your order, this requires a manual update by the Search Atlas team. You cannot edit the placement URL directly from within the platform. Before reaching out, please have the following ready: - Your Order ID and Placement ID - The current (incorrect) URL recorded in your order - The correct live URL where the article is published The team will process the update on your behalf once these details are provided. π¨ Reporting a Broken or Inaccessible Publisher Link If the URL on your placement is returning an error or the page is no longer accessible, this needs to be escalated to the publisher for review and repair. The Search Atlas team will contact the publisher directly to investigate and restore the link. Before reaching out, please confirm the issue is not temporary β try loading the URL again after a few minutes, ideally in a private/incognito browser window. If the link is consistently broken, have the following ready: - Your Order ID and Placement ID - The broken URL - The specific error you are seeing (e.g., 404, blank page, redirect loop) 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 Publisher Change for Niche Mismatch
If one or more of your in-progress links has been matched with a publisher whose website is not relevant to your niche β or whose content you do not want your brand associated with β you can request a publisher change. Because these links are already in progress, you cannot edit the publisher assignment directly from your dashboard. This article explains exactly what information to submit and how to confirm the request has been received and acted on. π οΈ Step-by-Step 1. Locate the affected links in your active link-building campaign. Note the full URL or domain of each publisher you want replaced, along with the target URL and anchor text associated with each link order. 2. Note the specific reason for the mismatch β for example, the publisher's niche, content type, or any brand-safety concern. The more detail you provide, the faster our team can find a suitable replacement. 3. Open the chat widget in the bottom-right corner of the platform and type human teammate to reach our support team directly. 4. Share the following in your message: the publisher domain(s) to be replaced, the link order ID(s) if visible in your dashboard, and a brief description of the niche mismatch or association concern. 5. Our team will pause or reassign the affected orders and confirm the new publisher options with you before proceeding. β How to Confirm It Worked After submitting your request, you should receive a confirmation from our team that the publisher assignment has been updated. To verify on your end, return to your active link-building campaign and check that the publisher domain(s) you flagged are no longer listed against those orders. If the orders still show the original publisher after 24 hours, follow up in the same chat thread with your order details so our team can escalate. 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 Low-Quality or Broken Link Lab Articles
π Overview Link Lab articles are generated automatically and placed on third-party sites to build backlinks. Occasionally, articles may be low quality, irrelevant to the linked business, or render with broken formatting. In rare cases, an unexpected billing charge may also appear on your account. This article explains what to do in each situation. β οΈ Known Issue: Article Quality and Broken Rendering Our engineering team has identified and resolved a bug that caused Link Lab articles to ignore Brand Vault information during generation, resulting in irrelevant content and broken page rendering (missing headers). This fix has been deployed. If you submitted your Brand Vault details before this fix, your existing articles may still be affected. What was fixed: Article generation now correctly reads Brand Vault data, and broken page rendering has been resolved. If your articles were generated before the fix: Affected orders can be regenerated. You will need to contact our support team to request regeneration β this cannot be triggered from within the platform at this time. β Before Contacting Support: Check Your Brand Vault To give your articles the best chance of being relevant and accurate, make sure your Brand Vault is fully populated before new articles are generated. A complete Brand Vault helps the AI understand your business, tone, and target audience. 1. Log in to your Search Atlas account. 2. Navigate to your Brand Vault and confirm that all business details, keywords, and brand descriptions are filled in and up to date. 3. If anything is missing or outdated, update it now so future articles reflect the correct information. π What to Do If Your Articles Are Low-Quality or Broken If you have already checked your Brand Vault and your Link Lab articles are still irrelevant, missing headers, or otherwise broken, follow these steps: 1. Note the specific article titles or order numbers that are affected. 2. Contact our support team through the chat option available in the platform. 3. Share the affected order numbers and describe the issue (e.g., irrelevant content, broken rendering, missing headers). 4. Our team will review the articles, file a ticket with the engineering team if needed, and arrange for the affected orders to be regenerated and reposted. Refund or deletion requests: If a regenerated article is still not acceptable, you can request that the article be deleted and a refund issued for that placement. Our support team can process this on your behalf. π³ What to Do About an Unexpected Charge If you see an unexpected charge on your account β for example, an add-on renewal you did not intend to activate β our support team can cancel and reverse it. 1. Open the chat option available in the platform and reach out to our support team.
π Link Lab Wrong Placement Refund and Removal
π Overview Link Lab orders are fulfilled by third-party publishers, and in rare cases a backlink placement may appear on a domain that does not match the site you ordered. If you received a placement on an irrelevant, low-quality, or policy-violating domain instead of the one you selected, you may be eligible for a refund and, where possible, removal of the link. β οΈ What Counts as a Fulfillment Mismatch - Your order was placed for a specific domain but the backlink appeared on a completely different website. - The placement domain is a piracy site, link farm, or otherwise violates quality standards. - The published content or anchor placement does not reflect what was agreed at checkout. π What to Do Immediately 1. Gather your order details. Note your order ID, the domain you originally selected at checkout, and the domain where the link was actually placed. You can find this information inside your Link Lab order history. 2. Take screenshots. Capture proof of the incorrect placement, including the live URL where the backlink appears. 3. Contact support as soon as possible. Refunds and removals are time-sensitive. Orders that were completed a significant time ago may no longer be eligible for a refund or link removal (see the policy section below). π° Refund Policy for Mismatched Orders When a fulfillment mismatch is confirmed by our team, a refund can be issued for the affected order. Please be aware of the following: - Eligibility window: Refunds can only be processed for recent orders. If an order was completed a significant time before you raise the dispute, we may be unable to issue a refund. - Act quickly: Submit your dispute as soon as you identify the mismatch to preserve your eligibility. ποΈ Link Removal Requests If you need the incorrectly placed backlink removed from the publisher's site, our team will escalate the removal request internally on your behalf. Please note: - Link removal is coordinated internally and depends on the publisher's cooperation. - Removal cannot be guaranteed for orders that were completed a long time ago. - Raising the issue promptly gives the best chance of a successful removal. If you believe you have received a fulfillment mismatch, please reach out to our support team with your order ID, the domain you selected, and evidence of where the link was actually placed. We're here to help resolve the issue as quickly as possible.
π οΈ Content Genius to Link Lab: Troubleshooting Article Submission Failures
When a Content Genius article submission to a Link Lab publisher fails, the cause is almost always one of a handful of fixable issues. Follow the steps below to identify and resolve the error without losing your article. Created your order through the AI Agent chat instead of directly inside Content Genius? AI Agent-generated Link Lab orders follow a separate flow with their own known issues (such as the article not appearing on the order page). See the AI Agent Link Lab troubleshooting article instead of this guide. β οΈ Known issue (May 2026) β Wix, HubSpot, and Webflow connections: Customers submitting articles through Wix, HubSpot, or Webflow UCMS integrations may currently see validation errors such as content_type is required, member_id is required, meta.collection_id is required, or Unsupported content_type None. This is a platform-side regression (ticket CG-1722) and cannot be resolved by changing your article. Contact Search Atlas support rather than attempting to self-fix. This notice will be removed once the fix ships to production. π How the Content Genius β Link Lab Submission Works The Content Genius to Link Lab workflow lets you send a finalized article directly to a publisher placement you have secured in Link Lab. When you click Submit to Link Lab inside Content Genius, the platform runs three checks in sequence: 1. Validates that the article includes all required fields (title, body, target URL, anchor text). 2. Authenticates your account's Link Lab access and publisher permissions. 3. Packages the article and delivers it to the selected publisher queue in Link Lab. A failure at any of these three steps produces a submission error. The sections below map each failure point to its fix. β οΈ Common Causes of Submission Failures Match your on-screen error text to one of these known causes before working through the full troubleshooting steps: - Missing required fields β The article is missing a title, body text, target URL, or anchor text. The submission validator blocks incomplete articles. Typical error: Missing required field: anchor text or Missing required field: target URL. - Article status not set to Complete β Content Genius requires the article status to be Complete before the Submit to Link Lab button activates. Open your article in Content Genius, click the Status dropdown in the top-right panel (options: Draft, In Progress, Needs Review, and Complete), select Complete, and save. The Submit to Link Lab button activates after you save. Typical error: Article must be marked Complete before submission. - No publisher selected or publisher connection lost β If the Link Lab publisher was removed, paused, or never linked, the submission has no destination. Typical error: Publisher not found or No active publisher selected for this article. - Insufficient account permissions β Your user role may not include Link Lab submission rights. Only an account admin can grant this access. Typical error: You do not have permission to submit articles. - Session timeout β A long editing session can expire your authentication token. Refreshing the page re-authenticates you without losing saved content. Typical error: Session expired. Please refresh and try again or 401 Unauthorized. - Duplicate submission β Link Lab blocks articles already submitted to the same publisher placement to prevent accidental double-publishing. Typical error: Duplicate submission detected for this publisher placement. π οΈ Step-by-Step: Fix a Failed Submission Work through these steps in order. Most submission failures resolve by step 4. 1. Confirm all required fields are filled in Content Genius. Open the article and verify all four fields are present: article title, body content (minimum word count met), target URL, and anchor text. Save the article after filling in any missing field. 2. Set the article status to Complete. In the Content Genius editor, open the Status dropdown in the top-right panel and select Complete. The Submit to Link Lab button activates only when status is set to Complete. 3. Verify the publisher is active in Link Lab. Go to Link Lab β Publishers and confirm the target publisher shows a status of Active. If the publisher shows Paused or Disconnected, re-activate it before retrying the submission. 4. Refresh your session and resubmit. Save the article, hard-refresh the page (Ctrl+Shift+R on Windows / Cmd+Shift+R on Mac), reopen the article, and click Submit to Link Lab again. A session refresh resolves most transient authentication errors. 5. Check for a duplicate submission. In Link Lab, go to Submissions β All Submissions and search for the article title. If a prior submission already exists for this publisher placement, Link Lab blocks the new one. Confirm receipt of the earlier submission with your publisher before creating a replacement. If none of these steps resolve the error, check your account permissions in the next section. π Check Account Permissions for Link Lab Submission Link Lab submission access is controlled at the user-role level. If you see "You do not have permission to submit articles", or the Submit to Link Lab button remains grayed out after the article is marked Complete, your role is missing the required permission. To check and update permissions: 1. Ask your account admin to go to Settings β Team β Roles. 2. Select your role and locate the Link Lab β Submit Articles permission toggle. 3. Enable the toggle and click Save. 4. Log out, then log back in for the permission change to take effect. After logging back in, retry the submission. A green Submission Successful confirmation banner appears at the top of the Content Genius editor when the article delivers correctly. π What to Include When Contacting Support If you have completed all steps above and the submission still fails, contact Search Atlas support. Include the following to speed up resolution: - Your account email address - The article name as it appears in Content Genius - The publisher name or publisher ID in Link Lab - The exact error message displayed (a screenshot is ideal) - The date and time of the failed submission attempt - A screen recording or JAM video of the failure, if available - The CMS integration in use, if any (Wix, HubSpot, Webflow) β relevant for the CG-1722 known issue The Search Atlas support team will review the Content GeniusβLink Lab bridge logs tied to your account and escalate to engineering if a platform-side issue is identified. π― You now know how to diagnose and resolve Content Genius to Link Lab submission failures β from missing required fields and session timeouts to permissions gaps and duplicate submissions. To learn more about setting up and managing your publisher placements, see the Link Lab Publishers guide.
π Understanding Placement Statuses: Publication-Unavailable vs Publisher-Rejected in Link Laboratory
When a placement in Link Laboratory requires your attention, it shows a Pending Action prompt. Two distinct statuses can trigger this prompt β publication-unavailable and publisher-rejected β and each has a different cause and a different path forward. π What Each Placement Status Means Link Laboratory tracks the state of every placement you request. When something blocks a placement from moving forward, the status updates automatically and a Pending Action prompt appears for you to review. - Publication-unavailable β SearchAtlas deactivated and removed the publication from its network. The site is no longer available to any campaign, regardless of publisher willingness. - Publisher-rejected β The publisher reviewed your placement request and actively declined it. The site remains in the SearchAtlas network and may accept placements from other campaigns. Both statuses require you to take action before the placement can continue β which is why both trigger a Pending Action prompt. β οΈ Publication-Unavailable: Cause and Next Steps A publication-unavailable status means SearchAtlas removed the site from its publisher network. This is not a decision made by the publisher β it is a network-level change by SearchAtlas, such as a quality review, policy update, or site removal request. Because the publication no longer exists in the network, your placement cannot be fulfilled on that site under any circumstances. 1. Open the affected placement in Link Laboratory. 2. Review the Pending Action message, which confirms the publication was removed from the network. 3. Select a replacement publication from the available inventory. 4. Submit your selection to resume the placement process. After you submit a replacement, the Pending Action prompt clears and your placement re-enters the standard fulfillment flow. π« Publisher-Rejected: Cause and Next Steps A publisher-rejected status means the publisher reviewed your specific placement request and chose not to accept it. The publication itself is still active in the SearchAtlas network β only your particular request was declined. Publishers may decline a placement due to content mismatch, niche restrictions, or capacity limits. SearchAtlas does not share the publisher's specific reason for declining. 1. Open the affected placement in Link Laboratory. 2. Review the Pending Action message, which confirms the publisher declined your request. 3. Select a replacement publication from the available inventory, or refine your targeting criteria to find a better-matched site. 4. Submit your selection to continue the campaign. After you submit a replacement, your new placement request enters the publisher review queue as normal. π Key Differences Between the Two Statuses - Who triggered it: Publication-unavailable is triggered by SearchAtlas; publisher-rejected is triggered by the publisher. - Is the site still in the network? No for publication-unavailable; yes for publisher-rejected. - Can you resubmit to the same site? No for publication-unavailable; potentially yes for publisher-rejected in a future campaign. - Required action for both: Select a replacement publication to resolve the Pending Action prompt and keep your campaign moving. π― Now that you understand the difference between publication-unavailable and publisher-rejected, you can respond to each Pending Action prompt with confidence and keep your link building campaigns on track. For more on managing your placements, see the Link Laboratory overview article.
π Resolve a Website Ownership Conflict
π Why this happens Search Atlas prevents duplicate website listings to protect site data and workspace access. You may see an ownership conflict when the website is already connected to another workspace, was added by a former team member, or is listed under a different version of the domain. β Check the website details 1. Open Website Studio from the left sidebar. 2. Confirm that you entered the correct domain, including the spelling and domain extension. 3. Check whether the website uses a different version, such as www versus the root domain, or a different subdomain. 4. Do not create a second listing for the same website. π οΈ Verify your ownership Make sure you can access the website or its domain settings. If Search Atlas provides an ownership verification step, complete it using the available instructions. The verification must be added to the exact website version shown in the platform. If you manage the website through a team, confirm that you have permission to edit its files, DNS settings, or connected publishing account. Being the website owner does not always mean your Search Atlas account has access to an existing listing. π₯ Request access from the current owner If another workspace already contains the website, contact the person who originally added it and ask them to review the listing and provide access or remove it if it is no longer needed. This is usually the fastest way to resolve a legitimate shared-ownership situation. If the website belongs to a previous employee, agency, or workspace, gather proof that you control the domain and identify the existing listing details before requesting a transfer or correction. π« Avoid common mistakes - Do not repeatedly submit the same website. - Do not add a temporary subdomain to bypass an ownership conflict. - Do not remove verification records unless you understand which listing they belong to. - Confirm that you are working in the correct Search Atlas workspace. π¬ Get help resolving the conflict If the website is yours but remains unavailable after checking the details and completing verification, include the domain, the Search Atlas workspace you are using, and a screenshot of the conflict message when requesting help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
π Resolve Website Ownership Conflicts
π Why the conflict appears Search Atlas prevents the same website from being added more than once when it is already associated with another listing, workspace, or account. This can happen even when you are the website owner. Common causes include: - The website was previously added by you or a teammate. - The domain is listed under another Search Atlas workspace. - You are adding a different version of the same site, such as www versus the root domain. - An old or duplicate listing still exists. π§ Check your existing listings 1. Open Website Studio from the left sidebar, or go to /website-studio. 2. Review your website listings and search for the domain. 3. Check common variations, including the root domain, www version, HTTP, and HTTPS. 4. Open the existing listing to confirm whether it is the site you want to manage. β Confirm the correct website Compare the listing with your websiteβs address. Make sure you are not trying to add a subdomain, folder, or alternate URL as a separate website when it belongs to an existing domain listing. If the existing listing is in your workspace, continue using it instead of creating another one. This keeps your website data and settings together. π Request a listing correction If the site belongs to you but is attached to another workspace or account, do not create a duplicate listing. Prepare the following information: - The exact website domain and URL variation. - The Search Atlas workspace where you want to manage it. - Proof that you control the website, if requested. - The name or location of any existing listing you found. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. β οΈ Avoid duplicate listings Do not repeatedly retry the same domain or create multiple variations to bypass the conflict. Duplicate entries can split your website data and make ownership harder to resolve. Use one accurate listing and ask our team to review ownership when the website is already claimed elsewhere.
π οΈ Resolve Unusable Publication Sites
π Why publication stops A Zia Tile article can remain unassigned when its selected site is no longer usable. Common reasons include no active publication, a non-US publication, a farm-listed domain, or a failed validation rule. The assigner does not automatically replace a site selected in Publication Notes. This prevents Search Atlas from changing your publishing decision without approval. The article is therefore skipped during each hourly assignment run until a replacement is chosen. π What the replacement options mean Suggested sites come from the same assignment engine used for normal placement. Each option meets the applicable requirements, including: - The minimum ordered DA - DR and organic traffic requirements - The 2.5x price limit compared with the ordered DA - QP quality requirements - Your accountβs rejection history Options may have a DA above the ordered range. This is expected: the price limit is the effective ceiling, and additional authority can be beneficial. Sites are listed from least used to most used where possible. Topic evidence shown beside a site is a preference signal, not a requirement. It is based on reviewing the siteβs existing article titles. β How to resolve the articles 1. Review each article with an unusable current pin. 2. Compare the suggested domains, DA, price, prior usage, and topic evidence. 3. Choose one option for every article, or suggest another suitable site. 4. Provide the article ID and your choice, such as 200586 β 2. 5. Wait for the approved reassignment and updated Publication Note before the next assignment run. For multiple orders, include the order number and article ID to avoid confusion. You can choose different sites for different articles, even when they share the same order. π What happens after approval After your choices are confirmed, the articles are reassigned and their Publication Notes are updated. This prevents the hourly cron or cascade process from moving them again. Articles should then become eligible for normal placement, provided the replacement site remains active and passes validation. π‘ Prevent future delays - Review Publication Notes before submitting or pinning an article. - Avoid selecting sites without an active publication. - Confirm that the publication is US-based when that rule applies. - Recheck saved sites if an article remains unassigned across multiple runs. - Respond with one clear replacement choice per article. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
ποΈ Resolving Website Ownership Conflicts on Publication Media
π Overview If your website is already listed on the Publication Media platform under a different account, you may encounter an ownership conflict. This article explains why this happens, what you can do, and how our team resolves these disputes fairly and securely. β οΈ Why Ownership Conflicts Happen Ownership conflicts occur when a domain is registered in Publication Media by someone other than the true website owner. Common causes include: - A previous agency, partner, or contractor submitted the site on your behalf - A reseller or third party listed your domain without your knowledge - A former employee registered the site under their own account - Duplicate submissions during platform migrations or onboarding Regardless of how the conflict arose, Search Atlas takes domain ownership seriously. Only the verified owner of a domain has the right to control its listing. β How Ownership Is Verified To establish rightful ownership, our team uses a domain ownership verification process. This involves confirming that you have direct access to and control over the domain in question. Our support team will guide you through the specific verification steps required for your situation. π οΈ Steps to Claim Your Website 1. Do not create a duplicate listing. Submitting the same domain twice will not resolve the conflict and may delay the process. 2. Gather your proof of ownership. Be ready to demonstrate that you are the rightful owner of the domain. Having access to your domain registrar or hosting account may be helpful. 3. Contact our support team. Open the chat widget and request an ownership conflict review. Provide your domain name and be ready to complete the verification steps our team assigns. 4. Complete the verification challenge. Our team will provide specific instructions. Follow them as directed and notify the team when you have done so. 5. Await confirmation. Once verified, our team will update the listing to reflect your ownership. The previous account's access to that domain will be reviewed and adjusted accordingly. π What to Expect During the Review Our team will: - Review the history of the domain listing on Publication Media - Issue a verification challenge only you β as the true owner β can complete - Update the domain's ownership record once verification is successful - Notify you when the transfer is complete and your site is live under your account Please note that for security reasons, we cannot transfer or remove a listing based on a claim alone. Verification is always required. π‘ Tips for a Smooth Resolution - Have your domain name ready when you contact support - Be prepared to demonstrate access to the domain or its associated accounts - Respond promptly to any instructions our team provides to avoid delays If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
π οΈ Resolve Order Alternative Disputes
π Understand order alternatives If a publication or placement cannot fulfill your order, Search Atlas may offer alternative options. An alternative is not automatically fulfilled unless it is selected and confirmed for the affected order item. If you provided alternatives for both items, review each item separately. One accepted alternative does not confirm or replace the other item. π Review your order 1. Open the order from the order notification or select Go to Orders. 2. Open the specific order and review each itemβs status. 3. Check whether the original publication was rejected, an alternative was selected, or the item is still awaiting fulfillment. 4. Compare the selected publication, service, price, and fulfillment status with what you purchased. π Select an alternative When an item is rejected and alternatives are available, open the alternatives list for that item. Review the publication details and any price difference before selecting an option. - Select an alternative for every affected item. - Confirm your selection when prompted. - Return to the order and verify that the selected alternative appears on the item. - Do not assume that opening or previewing an alternative completes the selection. If no alternatives appear, the item may not currently have an eligible replacement. Record the order number and item details before contacting support. β Confirm fulfillment After selecting an alternative, monitor the item status in the order. Keep the order confirmation, selected publication, price details, rejection notice, and any fulfillment updates. These details help distinguish an unfulfilled item from an item that was completed with an approved alternative. βοΈ If the delivered item differs If you received something different from the confirmed order, do not place a duplicate order. First verify the item status and selected alternative, then document the difference clearly. - Record the order and item identifiers. - Note the original publication and the confirmed alternative. - Describe what was delivered and what was missing. - Include relevant status messages or screenshots from the platform. Submit these details through the platform chat so the team can review the order history and fulfillment record. Avoid making repeated changes while the issue is under review. π¬ Get help with a dispute For unresolved fulfillment, missing alternatives, incorrect order information, or payment-related questions, provide the order number and explain the issue for each item separately. The support team can review the available order records and clarify the next step. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
π Troubleshooting Marquee Publications List Discrepancies
This article explains why the number of publishers you see in the marquee publications list may not match the domain authority thresholds described in the feature overview β and how to check that you are viewing the correct set of listings. π Common Causes - Advertiser tab vs. Publisher tab: The publications area contains two separate tabs β one for advertisers and one for publishers. The high-DA marquee publishers (DA 90+) are listed under the publisher tab. If you are viewing the advertiser tab, you will see a different and typically smaller set of entries that does not reflect the full marquee inventory. - Active availability: Marquee publication slots are premium placements with limited availability. A publisher that qualifies by DA may temporarily appear unavailable or unlisted if all slots are currently filled or the publisher has paused intake. - Filters applied: Active filters β such as niche, language, or region β can reduce the visible list. A DA 90+ publisher may exist in the full inventory but be hidden by your current filter selections. - Inventory updates: The marquee list is updated periodically. A publisher described in documentation may have been added or reclassified after that content was written, causing a temporary mismatch between the description and live inventory. π οΈ Step-by-Step 1. Open the publications section of the platform. 2. Locate the tab or toggle that switches between Advertiser and Publisher views, and select the Publisher tab. 3. Clear all active filters (niche, region, language, DA range) to view the full unfiltered list. 4. Apply a Domain Authority filter set to 90 and above to isolate marquee-tier publishers. 5. Review the results. If only one publisher appears, note its name and DA score for reference when contacting support. 6. If you suspect the inventory description is outdated, take a screenshot of the current list and the feature description for comparison. β How to Confirm It Worked After switching to the Publisher tab and clearing all filters, the list should display the full available marquee inventory. When you then apply the DA 90+ filter, every result shown should meet that threshold. If the count still does not match what the feature description states, this confirms a documentation-to-inventory discrepancy rather than a navigation issue β and that information will help our team investigate. You have confirmed the correct view when: the Publisher tab is active, no extra filters are applied, and the DA filter is the only active constraint. 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 Publication Media Site Deactivation and Pricing
π Overview If your website has been deactivated by Publication Media or your pricing counteroffer requests have been repeatedly denied, this article explains what to do next. Because the specifics of site deactivation and counteroffer decisions depend on your individual listing, our support team will need to review your case directly. β Why Was My Site Deactivated or My Counteroffer Denied? Site deactivations and counteroffer denials on Publication Media can occur for a variety of reasons related to your listing's pricing, activity status, or compliance with platform standards. The exact reason is specific to your account and listing, and our team can look into it for you. π οΈ What to Do Next To get help resolving a deactivation or a denied counteroffer, please have the following information ready before contacting support: - Your site URL as listed on Publication Media - The exact error message or notification you received when your site was deactivated or your counteroffer was denied - The date(s) the deactivation or denial occurred - A description of the steps you have already taken (e.g., whether you have attempted to resubmit a counteroffer or update your listing price) Having these details ready will allow our team to investigate your listing and advise you on the correct next steps for your specific situation. 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 Publishing Integration Errors
π Overview When distributing a press release through Search Atlas to outlets like USA Today, the platform uses a third-party service called Signal Genesys to handle distribution. If the connection between Search Atlas and Signal Genesys becomes out of sync, you may see errors such as: - "Signal Genesys: The selected client ID is invalid" - "API Token is invalid" - A press release that appears to fail but is actually published This article explains what causes these errors, what to do when you see them, and how our team resolves them. β οΈ Why This Error Happens The Signal Genesys integration relies on an API token and client ID that link your Search Atlas account to the distribution network. These credentials can become invalid for several reasons: - The API token has expired or been rotated on the Signal Genesys side - The client ID associated with your account has changed - A temporary sync issue between Search Atlas and Signal Genesys has occurred This is an integration-level issue and cannot be resolved by changing settings inside your Search Atlas account. It requires our technical team to re-sync the connection on the backend. π What to Check Before Contacting Support Before reaching out, take a moment to confirm the following: 1. Check if your press release was actually published. In some cases, the error message appears even though the press release was successfully distributed. Check the status of the submission in question within your press releases section to see if it shows as published. 2. Check your distribution quota. Failed press releases do not consume your quota. If you see a failed status, your quota should remain intact and you can safely attempt to republish once the integration is fixed. 3. Note the exact error message. Copy the full error text so our team can identify the specific cause quickly. π οΈ How to Resolve the Error Because this issue requires a backend fix, the resolution steps are straightforward: 1. Do not repeatedly attempt to republish while the error is active. Multiple failed attempts can create duplicate submissions once the integration is restored. 2. Contact our support team using the chat widget described at the bottom of this article. Provide the press release title, the outlet you were publishing to, and the exact error message you received. 3. Our team will re-sync the Signal Genesys integration on your account. This typically involves refreshing the API token and verifying the client ID. 4. Once the fix is confirmed, return to your press releases section and republish the affected press release. Your quota will not have been affected by the failed 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.
π Fix a 401 Invalid API Token in Signal Genesys
π¨ What This Error Means When you attempt to publish a press release through Signal Genesys and see a 401 'API Token is invalid' error, it means Signal Genesys cannot authenticate your request. This is a credential issue, not a platform permission problem. The token you have entered is either incorrect, expired, or has not been saved properly. This error will always block publishing until the API token is corrected. A simple refresh or retry will not resolve it. π Common Causes - The API token was copied with an extra space at the beginning or end. - The token was regenerated in your press release distribution account but not updated in Signal Genesys. - The token was entered into the wrong field during setup. - The token has been revoked or expired by your distribution provider. - The integration was set up using a test token that is no longer valid in production. π οΈ How to Fix the Error 1. Log in to your press release distribution account and navigate to your account settings or API / developer section to locate your current API token. 2. Copy the token carefully. Click the copy button if one is available, rather than selecting the text manually. This reduces the risk of including hidden spaces or missing characters. 3. Open Signal Genesys, the separate site connected to Search Atlas via API key. 4. Locate the API key or credential field within Signal Genesys where your distribution provider token is stored. 5. Clear the existing token completely before pasting. Do not paste over the old value, as residual characters can cause validation failures. 6. Paste your new token and check that no spaces appear before or after it. 7. Save your settings. 8. Attempt to publish your press release again. If the token is valid, the 401 error will no longer appear and your submission will proceed. β How to Confirm Your Token Is Valid Before re-entering your token in Signal Genesys, verify it is active in your distribution provider's dashboard. Most providers display a status label such as Active, Enabled, or show a last-used date. If your token shows as expired, revoked, or is missing entirely, generate a new one from within that provider's platform and use the new value. If your provider requires you to set specific permissions for the token (such as publish or submit access), confirm those permissions are enabled. A token that exists but lacks the correct scope will still return a 401 error. π If You Recently Regenerated Your Token API tokens generated in your distribution provider's account must be manually updated in Signal Genesys β the integration does not refresh them automatically. Any time you regenerate or rotate your token on the provider side, repeat the steps above to update the value stored in Signal Genesys. 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 the Link Building Exchange SSO Link
This article explains what to do if the Link Building Exchange single sign-on (SSO) link inside Search Atlas does not work as expected. Because the specific cause of this issue is not fully documented, the steps below reflect the most common actions that resolve SSO access problems. If your issue is not resolved after following these steps, our support team can investigate further. What Is the SSO Link? The Link Building Exchange link inside Search Atlas uses single sign-on to authenticate you automatically into the linked tool. If the link fails, it is typically an access issue that our support team can resolve directly for your account. What to Do If the Link Does Not Work 1. Confirm you are actively signed in to Search Atlas before clicking the Link Building Exchange link. 2. Open the SSO link directly from within the Search Atlas platform rather than from a saved or external source. 3. Clear your browser cache and cookies, then sign back in to Search Atlas and try the link again. 4. Try opening the link in a different browser or in a private/incognito window to rule out a browser or session conflict. 5. If none of the above resolves the issue, contact support and have the following ready: your Search Atlas account email, the exact behavior or error message you see when clicking the link, the browser and device you are using, and the approximate time the issue occurred. 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.
π οΈ Publication Queue Removal Bug Explained
π What Is This Issue? A system bug caused some posts to be removed from the publication queue even after they had been successfully published on time. This affected customers who completed their posts within the required window but were incorrectly flagged, triggering an automated removal from the queue. If this happened to you, your post was published β the removal was a system error, not a reflection of your performance or eligibility for payment. βοΈ Why Did This Happen? Our publication queue system uses an automated pipeline to track post status and timing. A bug in this pipeline caused the system to incorrectly remove some posts from the queue even though they had been successfully published on time. Our engineering team identified the issue and worked to resolve it. β What Has Been Fixed? Our team has investigated and resolved the underlying system bug responsible for the incorrect queue removals. Affected posts were reviewed and corrected on the backend. π What Should You Do If This Affected You? If your post was published on time but was removed from the queue, follow these steps: 1. Confirm your post is live by visiting the published URL or checking your connected platform (e.g., Google Business Profile). 2. Take a screenshot or note the published date and time as evidence. 3. Have your project name, the affected post details, and any relevant timestamps ready when you reach out so our team can review and correct your queue status promptly. 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.
π οΈ Published Post Removed From Queue Explained
π What This Article Covers You published a post before its deadline, but you received an email saying the post is being removed from your queue for taking too long. This article explains why this happens, what it means for your payment, and the exact steps to take next. β οΈ Why You Received This Email Removal emails are sent automatically when the platform does not record a Published status for a post within the expected publishing window. In many cases, the post was actually published on time β the system simply did not register it before the deadline check ran. Common causes include: - Publishing pipeline delays: posts can remain in a Publishing state longer than usual while the queue works through a backlog. - Timing detection gaps: the post went live at its destination (for example, your website or Google Business Profile), but the confirmation did not sync back to the platform before the deadline check. - Status sync lag: a short delay between the moment content goes live and the moment your dashboard updates. These are timing issues on the platform side. This email is not a judgment on the quality of your work, and it does not cancel work you have already completed. π° What This Means for Your Payment If your post is live and publicly visible, you will still be paid. A removal email does not reverse payment for a post that was genuinely published on time. Once our team verifies the live post, it is restored to the payment queue and processed in the normal payment cycle. To qualify, the post must be live at its assigned URL and visible to anyone visiting that link, without requiring a login. Important: do not delete the live post. Our team needs it in place to verify publication and confirm your payment. π Steps to Resolve This 1. Confirm the post is live. Open the post URL in an incognito or private browser window to make sure it is publicly visible without logging in. 2. Copy the live link. Save the exact URL where the post appears, along with the date and approximate time it went live, if you have them. 3. Check the post status. Review the post in your dashboard. If it still shows Publishing, this confirms a sync delay rather than a publishing failure on your end. 4. Contact our team. Open the chat widget and share your live link so we can verify the post and restore it to the payment queue. π‘οΈ How to Reduce the Chance of This Happening - Publish several hours before the deadline rather than right at the cut-off, giving the system time to register the post. - After publishing, refresh your dashboard and confirm the status changes to Published before you close the tab. - Keep a copy of the live URL for every post you publish. - If a post appears stuck in Publishing for an extended period, contact us before the deadline so we can check the queue while there is still time. π¬ Still Need Help? Have your live post link ready, along with the title of the assigned post and the removal email you received. This helps us verify publication quickly and protect your payment. 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.
π Link Laboratory Submission Processing Times
π What βIn Progressβ means A Link Laboratory submission marked In Progress is moving through the publisher and editorial workflow. The publisher may still be reviewing, approving, scheduling, or placing the submission. β±οΈ How long processing takes There is no fixed or guaranteed timeframe for Link Laboratory submissions. Processing time varies by publisher, editorial review, availability, and the steps required before a placement is completed. Because each publisher follows its own process, a submission can remain in progress longer than expected without indicating a platform issue. β οΈ Reasons a submission may be delayed - The publication or editor has not completed its review. - The publication is temporarily inactive or unavailable. - The submission was rejected and requires follow-up or an alternative next step. - Additional scheduling or editorial changes are needed before placement. π How to check your submission 1. Open Authority from the left sidebar. 2. Select the relevant Link Laboratory area under the Authority section. 3. Review the submission status and available order details. If the submission has remained in progress longer than expected, have the order details ready so its status can be reviewed. An order-specific update may be needed when a placement has stalled, a publication is inactive, or a submission was rejected. π¬ Need an order-specific update? 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.
π Fix an Inactive Publication Site Verification Status
π§ Overview After adding your site to the Search Atlas Publisher Dashboard and placing the required ownership meta tag, you may notice the site still shows an Inactive status β even days or weeks later. This article explains why this happens and walks you through the steps to resolve it. β Why Is My Site Still Showing as Inactive? Verification is confirmed when Search Atlas detects and records a timestamp against your site's ownership meta tag (internally tracked as domain_ownership_verified_at). If that timestamp was never recorded β or if the platform cached an outdated verification state β your site will remain inactive despite the meta tag being correctly in place. A known issue caused some sites to display a stale verification status. The verification banner relied on an older data point (pending_validation) instead of the actual ownership timestamp, meaning sites that met the requirements were sometimes still shown as inactive or unverified. This has been addressed, but manually triggering re-verification is the fastest way to resolve lingering cases. β How to Re-Verify Your Site 1. Make sure your ownership meta tag is still present in the section of your site's homepage. Do not remove it. 2. Log in to Search Atlas and go to your Publisher Dashboard. 3. Locate the affected site in your site list. 4. Click Verify ownership on the site card or within the site's settings. 5. Wait a few moments while Search Atlas re-checks your meta tag and updates the verification timestamp. 6. Once successful, the site status will change from Inactive to Active. π οΈ Before You Re-Verify β Quick Checklist - Meta tag is present: The ownership meta tag must appear in the of your homepage, not just an inner page. - Meta tag is correct: Copy the tag directly from your Publisher Dashboard to avoid typos. - Page is publicly accessible: Search Atlas must be able to crawl your homepage. Ensure it is not password-protected or blocked by robots.txt. - No caching issues: If you recently added the tag, clear your site's server or CDN cache so the latest version of your page is served to crawlers. β±οΈ How Long Does Re-Verification Take? In most cases, clicking Verify ownership triggers an immediate check and the status updates within a few minutes. If the status does not update after 10β15 minutes, confirm the checklist above is fully satisfied and try again. π Checking Your Site Status You can monitor your site's verification status at any time from the Publisher Dashboard. If your site also appears under Site Metrics (left sidebar β Site Metrics), you can review domain-level data there once verification is confirmed. π¬ Still Need Help? If you have completed all the steps above and your site is still showing as inactive, 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.
ποΈ Fix Site Catalog Publisher Filtering Issues
π Overview The Find Publishers button in Site Catalog lets you discover relevant publishers for your website. In some cases, clicking this button may not trigger a publisher search β and a JavaScript error may appear in your browser. This article explains the most common causes and how to fix them. β οΈ Common Symptoms - Clicking Find Publishers does nothing β no results load and no search request is sent. - A JavaScript error appears in the browser console after clicking the button. - The publisher-search feature works for some websites but not others. π οΈ Step-by-Step Troubleshooting 1. Check your URL format. Make sure the website URL entered in Site Catalog is correctly formatted. Use the full domain without trailing slashes (e.g., quicksortindia.com rather than www.quicksortindia.com/). Inconsistent URL formats can prevent the publisher-search request from firing correctly. 2. Remove the "www" prefix if present. Some domains trigger a JavaScript parsing error when entered with the www. prefix. Try removing it and entering just the root domain (e.g., quicksortindia.com), then click Find Publishers again. 3. Clear your browser cache and cookies. Cached scripts can interfere with button functionality. Clear your cache, close and reopen your browser, then log back into Search Atlas and retry. 4. Try a different browser. Test the feature in an alternative browser (e.g., Chrome, Firefox, or Edge) to rule out browser-specific JavaScript conflicts. 5. Disable browser extensions. Ad blockers, privacy extensions, or script blockers can prevent publisher-search requests from being sent. Temporarily disable all extensions and try again. 6. Check for JavaScript errors in the console. Open your browser's developer tools (press F12), go to the Console tab, click Find Publishers, and note any red error messages. This information is helpful when contacting support. β Confirming the Fix After following the steps above, a successful publisher search will display a list of relevant publisher results below the Find Publishers button. No error messages will appear in the browser console, and the network request will complete without issue. π‘ Best Practices for Site Catalog - Always enter the root domain without "www" or trailing slashes when adding a site. - Use a modern, up-to-date browser for the best compatibility with Search Atlas features. - If you manage multiple sites, verify each one is correctly listed under Site Metrics (Left sidebar β Site Metrics β Overview) before using publisher filtering. π Still Need Help? If the Find Publishers button is still not working after completing the steps above, gather the JavaScript error message from your browser console and the exact URL you entered. 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.