WordPress database error: [Table 'wp_options' is marked as crashed and should be repaired]
SELECT option_value FROM wp_options WHERE option_name = 'debug_error_p61a1127d326c66fe47de04898744e9dc' LIMIT 1

WordPress database error: [Duplicate entry 'debug_error_p61a1127d326c66fe47de04898744e9dc' for key 'option_name']
INSERT INTO `wp_options` (`option_name`, `option_value`, `autoload`) VALUES ('debug_error_p61a1127d326c66fe47de04898744e9dc', 'a:1:{s:19:\"2021-12-05 00:01:03\";s:104:\"Error #1010: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to webportalhq.com:443 \";}', 'yes') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`)

WordPress database error: [Table 'wp_options' is marked as crashed and should be repaired]
SELECT option_value FROM wp_options WHERE option_name = 'debug_error_pb17dfb706b0f7810f499e85658ad990f' LIMIT 1

WordPress database error: [Duplicate entry 'debug_error_pb17dfb706b0f7810f499e85658ad990f' for key 'option_name']
INSERT INTO `wp_options` (`option_name`, `option_value`, `autoload`) VALUES ('debug_error_pb17dfb706b0f7810f499e85658ad990f', 'a:1:{s:19:\"2021-12-05 00:01:15\";s:104:\"Error #1010: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to webportalhq.com:443 \";}', 'yes') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`)


Strict Standards: Redefining already defined constructor for class Master_Admin in /home/firstone/public_html/wp-content/plugins/wp-master-admin/wp-master-admin.php on line 29

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/plugins/wp-master-admin/wp-master-admin.php on line 123

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/themes/mentor/framework/php/boot.php on line 35

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeGlobal.php on line 72

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/PeThemeGallery.php on line 288

Strict Standards: Only variables should be assigned by reference in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/Constant/PeThemeConstantGallery.php on line 9

Strict Standards: Only variables should be assigned by reference in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/Constant/PeThemeConstantVideo.php on line 13

Strict Standards: Only variables should be assigned by reference in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/Constant/PeThemeConstantProject.php on line 8

Notice: The called constructor method for WP_Widget in LayerSlider_Widget is deprecated since version 4.3.0! Use
__construct()
instead. in /home/firstone/public_html/wp-includes/functions.php on line 4510

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/PeThemeWGManager.php on line 29

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/PeThemeWGManager.php on line 40

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/Widget/PeThemeWidget.php on line 30

Strict Standards: Declaration of PeThemeWidgetTwitter::getContent() should be compatible with & PeThemeWidget::getContent(&$instance) in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/Widget/PeThemeWidgetTwitter.php on line 0

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "footer" sidebar. Defaulting to "sidebar-1". Manually set the id to "sidebar-1" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/firstone/public_html/wp-includes/functions.php on line 4778

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "default" sidebar. Defaulting to "sidebar-2". Manually set the id to "sidebar-2" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/firstone/public_html/wp-includes/functions.php on line 4778

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Contact" sidebar. Defaulting to "sidebar-3". Manually set the id to "sidebar-3" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/firstone/public_html/wp-includes/functions.php on line 4778

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Footer Alt" sidebar. Defaulting to "sidebar-4". Manually set the id to "sidebar-4" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/firstone/public_html/wp-includes/functions.php on line 4778

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Right Sidebar" sidebar. Defaulting to "sidebar-5". Manually set the id to "sidebar-5" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/firstone/public_html/wp-includes/functions.php on line 4778

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Left Sidebar" sidebar. Defaulting to "sidebar-6". Manually set the id to "sidebar-6" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/firstone/public_html/wp-includes/functions.php on line 4778

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Faq" sidebar. Defaulting to "sidebar-7". Manually set the id to "sidebar-7" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/firstone/public_html/wp-includes/functions.php on line 4778

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "SEO Articles" sidebar. Defaulting to "sidebar-8". Manually set the id to "sidebar-8" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/firstone/public_html/wp-includes/functions.php on line 4778

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Mobile Sidebar" sidebar. Defaulting to "sidebar-9". Manually set the id to "sidebar-9" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/firstone/public_html/wp-includes/functions.php on line 4778

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Website Marketing Sidebar" sidebar. Defaulting to "sidebar-10". Manually set the id to "sidebar-10" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/firstone/public_html/wp-includes/functions.php on line 4778

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "SEO Services" sidebar. Defaulting to "sidebar-11". Manually set the id to "sidebar-11" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/firstone/public_html/wp-includes/functions.php on line 4778

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/PeThemeSCManager.php on line 19

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/PeThemeSCManager.php on line 41

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/PeThemeSCManager.php on line 56

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/PeThemeSCManager.php on line 123

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/ShortCode/PeThemeShortcode.php on line 33

Deprecated: Assigning the return value of new by reference is deprecated in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/PeThemeContent.php on line 172
Indexed Pages in GoogleFirst One On

Indexed Pages in Google

Identifying Crawling Problems

Start your investigation by simply typing site:yoursite.com into the Google search bar. Does the number of results returned correspond with the amount of pages your site has, give or take? If there’s a a large gap in the number of results VS the actual number of pages, there might be trouble in paradise. (note – the number given by Google is only an estimate not an exact amount). You can use the SEO Quake plugin to extract a list of URLs that Google has indexed.

The very first thing you should have a look at is your Google Webmaster Tools dashboard. Forget about all the other tools available for a second. If Google sees issues with your site, then those are the ones you’ll want to address first. If there are issues, the dashboard will show you the error messages. See below for an example. I don’t have any issues with my sites at the moment, so I had to find someone else’s example screenshot.

Crawl Errors

The 404 HTTP Status code is most likely the one you’ll see the most. It means that whatever page the link is pointing to, cannot be found. Anything other than a status code of 200 (and a 301 perhaps) usually means there’s something wrong, and your site might not be working as intended for your visitors. A few great tools to check your server headers are URIvalet.com and the Screaming Frog SEO Spider and of course the SEOmoz crawl-test tools although that last one is for Pro member, and limited to two crawls per day.

Fixing Crawling Errors

Typically these kinds of issues are caused by one or more of the following reasons:

  1. Robots.txt – This text file which sits in the root of your website’s folder communicates a certain number of guidelines to search engine crawlers. For instance, if your robots.txt file has this line in it; User-agent: * Disallow: / it’s basically telling every crawler on the web to take a hike and not index ANY of your site’s content.
  2. .htaccess – This is an invisible file which also resides in your WWW or public_html folder. You can toggle visibility in most modern text editors and FTP clients. A badly configured htaccess can do nasty stuff like infinite loops, which will never let your site load.
  3. Meta Tags – Make sure that the page(s) that’s not getting indexed doesn’t have these meta tags in the source code: <META NAME=”ROBOTS” CONTENT=”NOINDEX, NOFOLLOW”>
  4. Sitemaps– Your sitemap isn’t updating for some reason, and you keep feeding the old/broken one in Webmaster Tools. Always check, after you have addressed the issues that were pointed out to you in the webmaster tools dashboard, that you’ve run a fresh sitemap and re-submit that.
  5. URL Parameters – Within the Webmaster Tools there’s a section where you can set URL parameters which tells Google what dynamic links you do not want to get indexed. However, this comes with a warning from Google: “Incorrectly configuring parameters can result in pages from your site being dropped from our index, so we don’t recommend you use this tool unless necessary.”
  6. You don’t have enough Pagerank – lolwut? Matt Cutts revealed in an interview with Eric Enge that the number of pages Google crawls is roughly proportional to your pagerank.
  7. Connectivity or DNS issues – It might happen that for whatever reason Google’s spiders cannot reach your server when they try and crawl. Perhaps your host is doing maintenance on their network, or you’ve just moved your site to a new home, in which case the DNS delegation can stuff up the crawlers access.
  8. Inherited issues – You might have registered a domain which had a life before you. I’ve had a client who got a new domain (or so they thought) and did everything by the book. Wrote good content, nailed the on-page stuff, had a few nice incoming links, but Google refused to index them, even though it accepted their sitemap. After some investigating, it turned out that the domain was used several years before that, and part of a big linkspam farm. We had to file a reconsideration request with Google.

Some other obvious reasons that your site or pages might not get indexed is because they consist of scraped content, are involved with shady linkfarm tactics, or simply add 0 value to the web in Google’s opinion (think thin affiliate landing pages for example).


Strict Standards: Declaration of Walker_Comment_PE::start_lvl() should be compatible with Walker_Comment::start_lvl(&$output, $depth = 0, $args = Array) in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/PeThemeComments.php on line 0

Strict Standards: Declaration of Walker_Comment_PE::end_lvl() should be compatible with Walker_Comment::end_lvl(&$output, $depth = 0, $args = Array) in /home/firstone/public_html/wp-content/themes/mentor/framework/php/PeTheme/PeThemeComments.php on line 0