=== WordPress Importer === Contributors: wordpressdotorg Donate link: https://wordpressfoundation.org/donate/ Tags: importer, wordpress Requires at least: 3.6 Tested up to: 4.9 Stable tag: 0.6.4 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html Import posts, pages, comments, custom fields, categories, tags and more from a WordPress export file. == Description == The WordPress Importer will import the following content from a WordPress export file: * Posts, pages and other custom post types * Comments * Custom fields and post meta * Categories, tags and terms from custom taxonomies * Authors For further information and instructions please see the [Codex page on Importing Content](https://codex.wordpress.org/Importing_Content#WordPress) == Installation == The quickest method for installing the importer is: 1. Visit Tools -> Import in the WordPress dashboard 1. Click on the WordPress link in the list of importers 1. Click "Install Now" 1. Finally click "Activate Plugin & Run Importer" If you would prefer to do things manually then follow these instructions: 1. Upload the `wordpress-importer` folder to the `/wp-content/plugins/` directory 1. Activate the plugin through the 'Plugins' menu in WordPress 1. Go to the Tools -> Import screen, click on WordPress == Changelog == = 0.6.4 = * Improve PHP7 compatibility. * Fix bug that caused slashes to be stripped from imported comments. * Fix for various deprecation notices including `wp_get_http()` and `screen_icon()`. * Fix for importing export files with multiline term meta data. = 0.6.3 = * Add support for import term metadata. * Fix bug that caused slashes to be stripped from imported content. * Fix bug that caused characters to be stripped inside of CDATA in some cases. * Fix PHP notices. = 0.6.2 = * Add `wp_import_existing_post` filter, see [Trac ticket #33721](https://core.trac.wordpress.org/ticket/33721). = 0.6 = * Support for WXR 1.2 and multiple CDATA sections * Post aren't duplicates if their post_type's are different = 0.5.2 = * Double check that the uploaded export file exists before processing it. This prevents incorrect error messages when an export file is uploaded to a server with bad permissions and WordPress 3.3 or 3.3.1 is being used. = 0.5 = * Import comment meta (requires export from WordPress 3.2) * Minor bugfixes and enhancements = 0.4 = * Map comment user_id where possible * Import attachments from `wp:attachment_url` * Upload attachments to correct directory * Remap resized image URLs correctly = 0.3 = * Use an XML Parser if possible * Proper import support for nav menus * ... and much more, see [Trac ticket #15197](https://core.trac.wordpress.org/ticket/15197) = 0.1 = * Initial release == Upgrade Notice == = 0.6 = Support for exports from WordPress 3.4. = 0.5.2 = Fix incorrect error message when the export file could not be uploaded. = 0.5 = Import comment meta and other minor bugfixes and enhancements. = 0.4 = Bug fixes for attachment importing and other small enhancements. = 0.3 = Upgrade for a more robust and reliable experience when importing WordPress export files, and for compatibility with WordPress 3.1. == Frequently Asked Questions == = Help! I'm getting out of memory errors or a blank screen. = If your exported file is very large, the import script may run into your host's configured memory limit for PHP. A message like "Fatal error: Allowed memory size of 8388608 bytes exhausted" indicates that the script can't successfully import your XML file under the current PHP memory limit. If you have access to the php.ini file, you can manually increase the limit; if you do not (your WordPress installation is hosted on a shared server, for instance), you might have to break your exported XML file into several smaller pieces and run the import script one at a time. For those with shared hosting, the best alternative may be to consult hosting support to determine the safest approach for running the import. A host may be willing to temporarily lift the memory limit and/or run the process directly from their end. -- [WordPress Codex: Importing Content](https://codex.wordpress.org/Importing_Content#Before_Importing) == Filters == The importer has a couple of filters to allow you to completely enable/block certain features: * `import_allow_create_users`: return false if you only want to allow mapping to existing users * `import_allow_fetch_attachments`: return false if you do not wish to allow importing and downloading of attachments * `import_attachment_size_limit`: return an integer value for the maximum file size in bytes to save (default is 0, which is unlimited) There are also a few actions available to hook into: * `import_start`: occurs after the export file has been uploaded and author import settings have been chosen * `import_end`: called after the last output from the importer Google’s Search Liaison Addresses Brand Bias Concerns – Reflex The Best

Google’s Search Liaison Addresses Brand Bias Concerns


In a recent interview with Aleyda Solis, Google’s Search Liaison, Danny Sullivan, discussed the company’s approach to ranking smaller websites versus larger brands.

This topic has long been a point of contention, with concerns that Google’s ranking systems favor brands over independent sites.

Fairness In Search Results

Sullivan claims that Google doesn’t inherently favor brands, stating:

“Our ranking systems aren’t saying ‘are you a big brand therefore you rank’… The core of it isn’t really whether you’re big or you’re small, the core of it is whether you have the most useful, the most relevant, most satisfying information.”

The Perception Problem

Despite Google’s stance, Sullivan acknowledged the widespread perception that larger, well-established sites have an advantage in search results.

He recognized the frustration of smaller site owners who feel they cannot compete with bigger brands for visibility.

Sullivan states:

“I have looked at cases where people say you don’t like small sites, and I am not taking away from any of the real concerns because they are there… I wish they were doing better, but I can also see co-occurring in some of the same queries that I’m given other independent sites that are doing well.”

Challenges & Improvements

Sullivan admitted that Google’s systems sometimes fail to recognize high-quality content from smaller sites.

He assured that the company is actively improving this aspect of its algorithms.

Sullivan said:

“We don’t want it to be only the very big things rank well and I think in the last update we did talk about how we were taking in a lot of these concerns and trying to understand how we can do more for some of the smaller sites, the so-called independent sites.”

Advice For Smaller Sites

For independent website owners feeling discouraged, Sullivan offered some advice: focus on developing your brand.

He advised:

“If you’re a smaller site that feels like you haven’t really developed your brand, develop it. That’s not because we’re going to rank you because of your brand, but because it’s probably the things that cause people externally to recognize you as a good brand may in turn co-occur or be alongside the kinds of things that our ranking systems are kind of looking to reward.”

On advice for content creators, Sullivan adds:

“Just keep listening to your heart and doing what it is that you think is the right thing to be doing… Our ranking systems are trying to reward great content that’s made for people and if you feel like you’re doing that, then we’re going to try to catch up to you.”

Looking Ahead

Google appears to be taking these concerns seriously.

Sullivan mentioned that recent updates have aimed to do more for smaller sites. However, he maintains that Google’s goal is to show the best content regardless of brand recognition.

While challenges remain, Google’s acknowledgment of the issue and efforts to improve suggests a potential shift with future updates.

Hear Sullivan’s full statements in the video below:


Featured Image: rudall30/Shutterstock



Source link

tech
We will be happy to hear your thoughts

      Leave a reply

      Reflex The Best
      Logo