Skip to contentSkip to main navigation Skip to footer

Articles

Squirrly SEO - Error Messages

Squirrly SEO – Error Messages

Login Error Messages

These messages show on Squirrly > First Step, the screen where you sign up or log in to connect the site to Squirrly Cloud.

We found your email, so it means you already have a Squirrly.co account.

It means that you already have an account with Squirrly SEO and you need to login by clicking the button I already have an account and use the same email address and the password.

If you lost your password you can reset it from Lost Password page.


Wrong email or password!

The email or the password you typed on the login form doesn’t match your Squirrly account. Check both and try again, or reset the password from the Lost Password page.


You can only use this account for the URL you registered first!

Squirrly Cloud sends this message on login when the account can’t be used for this website’s address. Contact us with the site URL and the account email so we can check it.


Your email is not valid. Please enter a valid email.

It means that your email account does not contain a correct format. Enter a valid email to connect to Squirrly Cloud.


We could not create your account. Please enter a valid email.

It means that your email account does not contain a correct format. Enter a valid email to connect to Squirrly Cloud.


Squirrly Cloud is temporarily unavailable and couldn’t process the request. Please try again in a few minutes – details are shown under the form.

Your website couldn’t reach Squirrly Cloud, or the Cloud answered the sign-up or the login with a server error (HTTP 500 or higher). Wait a few minutes and try again. The debug box under the form shows what happened.


Squirrly Cloud didn’t return the login data. See the debug details under the login form.

The Cloud replied, but not with the login data the plugin expects. The box under the form, “Last Squirrly Cloud error (debug details, secrets are masked)”, shows the full reply for one hour to administrators. If that reply is an HTML page or is empty, the request never reached the Squirrly API: a firewall, a security plugin or the host blocked it. Send those details to our support team.


Error: Couldn’t connect to host 🙁 . Please contact your site’s webhost (or webmaster) and request them to add https://api.squirrly.co/v2/ to their IP whitelist.

There are hosting servers or security plugins that don’t allow remote connections from your website.
If you receive this error message please contact your WebHost and ask them to allow outgoing connections to api.squirrly.co and to whitelist our cloud IP addresses:

5.161.83.61 (the crawler, for audits and page checks)
195.201.232.57 (the Squirrly Workers, for robots.txt, sitemap.xml, llms.txt, the favicon and the WordPress REST API)
128.140.57.69 (the API server, for checks you start from the plugin or the Cloud)

Then try again!


You disconnected your website from https://cloud.squirrly.co/

Our Cloud App cloud.squirrly.co offers you the option to disconnect a website from the cloud and reconnect with a different email address.

If you already disconnected a website, if you connect using the same email address, you will receive this error message.
If you want to connect using the same email address, reconnect the website from the cloud.squirrly.co.


Plugin Error Messages

stream_socket_client(): Unable to connect to tcp://api.squirrly.co:80 (php_network_getaddresses: getaddrinfo failed: No such host is known. )

This error message means that you don’t have an internet connection or the connection between your website and Squirrly Cloud could not be established. Check your server firewall settings and make sure you’re not blocking remote connections.

Read more about this error here.


No working transports found

This error message occurs when there are missing PHP extensions on your server and WordPress is unable to make external HTTP requests.

You need to install the PHP extension php_openssl on your server so that WordPress can handle SSL requests.
You can also read more about this error here.


cURL error 60: SSL certificate problem: self signed certificate

This error message appears when the SSL certificate check on the connection to Squirrly Cloud fails.
Squirrly SEO doesn’t check the SSL certificate on its Cloud calls by default: the constant SQ_CHECK_SSL is false unless you set it. If you see this error, open the wp-config.php file and look for this line:

define('SQ_CHECK_SSL', true);

Remove it, or change it to:

define('SQ_CHECK_SSL', false);

cURL error 28: Operation timed out after … milliseconds with 0 bytes received

This error message appears when there is a slow network connection with Squirrly Cloud. This usually happens when the Cloud has too many API calls and can’t serve all the requests.

Most calls to Squirrly Cloud wait 20 seconds (20000 milliseconds) for an answer before they stop with this error. A few longer calls, such as loading the Briefcase, wait 60 seconds.

This error appears very rarely and the timeout issue will disappear in a few minutes.


cURL error 6: Could not resolve host: api.squirrly.co

This error message appears when you use a localhost website and there is a local network connection issue. Please check the network connection and try again.


This website can’t reach Squirrly Cloud right now. Refresh the page in a minute. If the message stays, ask your host to allow outgoing connections to api.squirrly.co.

The Live Assistant shows this message in the post editor when the site can’t reach Squirrly Cloud. Refresh the page after a minute. If it stays, ask your host to allow outgoing connections to api.squirrly.co, the same fix as for “Couldn’t connect to host” above.


This site needs to reconnect to Squirrly Cloud

The plugin shows this screen when the website was cloned, staged or moved to a new address, so Squirrly Cloud can no longer verify it. Click Reconnect this site. How Can I Change My Squirrly Account? has more on reconnecting.


An error occured while connecting. Error: Invalid token. Close this tab and try to connect again in the plugin

This error can appear in regards to Google Analytics. To fix it, close that tab and click Sign in next to Google Analytics again in Squirrly > Technical SEO > Connect Tools. If the error stays, disconnect the site from Squirrly Cloud (Disconnect at the bottom of the account menu) and connect it again from Squirrly > First Step.


Contact Us

For any error message you receive during the registration process, login process or while using the Squirrly SEO plugin please contact us to investigate and make the Cloud connection better for you.

Compatibility with Polylang Plugin

Polylang plugin

Polylang is a WordPress plugin for bilingual and multilingual sites. You write posts and pages, create categories and tags as usual, and then set the language for each of them.

Squirrly SEO works with Polylang and with Polylang Pro. It reads the language Polylang set for each post and page, and which posts and pages have a translation in that language. When either plugin is installed, Squirrly > All Features also shows a Polylang card that links to this page.

What you get when you use Polylang with Squirrly SEO:

  • SEO meta fields for each language. Each translation is its own post in WordPress, so it has its own SEO Snippet and you can optimize every language version.
  • Posts listed by language. Bulk SEO lists the posts in the language you pick with the Polylang language switcher in the WordPress admin bar. If you have posts in English and posts in Spanish, you can show only the English ones or only the Spanish ones while you work in Squirrly > Optimize > Bulk SEO.
Bulk SEO with Polylang languages

Sitemap XML with Polylang

Go to Squirrly > Technical SEO > Tweaks & Sitemaps > Sitemap XML. There you can turn on Combine Languages in Sitemap.

The switch shows only when Polylang or Polylang Pro is installed, and only in the SEO Expert view.

With Combine Languages in Sitemap turned on, all languages go into the same sitemap.xml file.

Combine Languages in Sitemap switch

By default (switch off), each language gets its own sitemap.xml, and you add the language slug to the address, for example /en/sitemap.xml.

So all posts in English go into one sitemap.xml file and all posts in Spanish go into another one, as in the two examples below.

English sitemap.xml
Spanish sitemap.xml

The other sitemap settings are in Sitemap XML Settings.

Bulk SEO with Polylang

When a post or page has no translation in the Polylang default language, Squirrly shows this message: No Polylang translation for this post.

You can still optimize the Snippet, but it doesn’t belong to a translation in that language. Open the post in Edit Post and check the language Polylang set for it.

No Polylang translation for this post message

How to Inspect an URL with Google Search Console

How to Inspect an URL with Google Search Console

To access the Google Search Console for your website, go to https://search.google.com/search-console and select the website you want to check. If your website is not yet added on GSC, follow this tutorial to add a property on Google Search Console.

Once you get to your page on Google Search Console, add the URL or a Focus Page URL from Squirrly SEO that you want to inspect/verify and click Enter.

Once you get the URL status on Google Search Console, test the page by clicking the “Test Live URL” button.

If you get the message “URL is not on Google” it means that the URL was not yet indexed on Google and you need to ask Google to index it or wait until the Google crawlers get to your website.

Once you test the page with Google Live Test, you will see if the page is available to Google and if it has rich snippets.

If the page is available for Google, it will be indexed the next time the Google crawler checks your URL. Click “Request indexing” to ask Google to crawl it sooner.

Indexing isn’t instant, and Google doesn’t give a time for it. Inspect the URL again later to see if the status changed to “URL is on Google”.

Note! If the snippet is changed on your page after the page is indexed, you need to request a new index. Google will not send the crawlers again on the same day so you will probably see the new snippet in the next days.

Check and submit pages from Squirrly SEO

  • Inspect URL opens a report for one page. The link is in the row menu of Squirrly > Focus Pages and Squirrly > GEO Audit, and under each post in Posts > All Posts. Use it to check a page after a fix.
  • LLM Indexing sends new and updated URLs to IndexNow. With Google Search Console connected in Squirrly > Technical SEO > Connect Tools, the same URLs also go to the Google Indexing API. To send URLs by hand, go to Squirrly > LLM Indexing > Submit URLs.

How To Validate Website to Pinterest

How To Validate Website to Pinterest

Step 1. Go to your Pinterest profile and click on the edit button

Step 2. Click on “Settings” and “Claim”.

Step 3. “Confirm Website” button

Find the Confirm Website Button

Step 3. Copy the Code

Copy Meta Description

Step 4. Add the code to Squirrly > SEO Settings > Connections

Step 5. Save and validate at: https://developers.pinterest.com/tools/url-debugger/

Squirrly Live Assistant is Not Showing in Edit Post

Squirrly Live Assistant is built to show on every public post type while you’re in the Post Editor in the backend.

How it shows depends on the Live Assistant Type setting in Squirrly > Optimize > Settings (visible in SEO Expert mode): Auto, Integrated Box or Floating Box. The default is Auto.

With Floating Box, the Live Assistant loads on the right side of the screen as a floating box and you can move it from right to the left as you like. (simply click on the Assistant, Hold, and Drag it anywhere you want)

Squirrly Live Assistant as a floating box in the post editor

You can also minimize or close and re-open the Live Assistant anytime you want.

Minimize or close the Squirrly Live Assistant

With Integrated Box, the Live Assistant stays inside the Squirrly Live Assistant panel in the editor sidebar.


If you are in the Post Editor and Squirrly Live Assistant is not loading as it should please make sure that:

1. The post type is not selected in Exclusions in Squirrly > Optimize > Settings. Don’t select anything there if you want the Live Assistant to load for all post types. If any post type is selected, the Live Assistant doesn’t load for that post type.

Live Assistant Exclusions setting

2. The Squirrly Live Assistant panel is turned on if you use the Block Editor. Open the editor’s Options menu (the three dots at the top right), go to Preferences > Panels and switch on Squirrly Live Assistant.

Block Editor options menu

3. Your user role can optimize posts with Squirrly. The Live Assistant loads only for users with the Squirrly sq_manage_snippet capability. Administrators, Squirrly SEO Admins, Editors, Squirrly SEO Editors and any role that can edit posts (Author, Contributor) get it. See Squirrly User Roles.

4. No code turns it off. A theme or plugin that returns false on the sq_load_sla filter removes the Live Assistant from the editor. The list of hooks is in Deactivating Specific Features in Squirrly SEO Plugin Using Hooks.

5. The plugin is connected to Squirrly Cloud. If it isn’t, the box shows “To load the Live Assistant and optimize this page, click to connect to Squirrly Cloud.” Follow Connect to Squirrly Cloud, then reload the post.

If all of these are correct, the Live Assistant will show in the Post Editor. Other messages the box can show, and what they mean, are listed in the Live Assistant troubleshooting section.

Before you leave

Future of AEO GEO and AI Search!

Free Now. Free Forever.

It’s time to stop orbiting SaaS.

Be the Meteor.

10 Elite Tools. 1 Stack.