=== 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 A European And An American Internet – Reflex The Best

A European And An American Internet


Regulation splits the internet experience, a.k.a. Search, into a European and American version with stark differences.

While big tech companies face complexity, Search players have an opportunity to compare SERP features and AI Overviews in both internet versions and better understand their impact.

AI on Innovation, I mentioned that:

Differences in AIO design might arise between the EU and non-EU countries. New regulations and fines lower the appetite for tech companies like Alphabet, Meta, or Apple to launch AI features in the EU. The result could be two internets that allow us to compare the impact and changing AI landscape in countries like the U.S.

The Digital Marketing Act (DMA) is the European Union’s tech gatekeeper regulation and is responsible for splitting the web by creating distinct experiences in the EU compared to the U.S.

It rules that companies can no longer force defaults on users (like a search engine or browser), show their offering above other marketplace participants, and serve targeted ads without consent. They must guarantee interoperability, data access, ad transparency, and side loading.

Seven gatekeepers experience significant circumcisions in their EU product versions: Alphabet, Amazon, Apple, Bytedance, Booking, Meta, and Microsoft.

Gatekeepers, as defined by the DMA (Image Credit: Kevin Indig)

In 2024, the DMA forked the Search experience:

1. Hotels And Flights

Google’s Hotel and Flight SERP feature is deemed “self-preferencing” under the DMA, which is why the modules look significantly different in the EU compared to the U.S.

Since March 2024, the EU SERP has shown “travel sites” and “hotel sites” boxes at the top with links to aggregators instead of Google’s own modules.

In the EU, Google shows “Flight sites” instead of its own flight search moduleIn the EU, Google shows “Flight sites” instead of its own flight search module. (Image Credit: Kevin Indig)
Further down the SERP, Google shows a selection of flights from different airlinesFurther down the SERP, Google shows a selection of flights from different airlines. (Image Credit: Kevin Indig)

The impact seems to favor online travel agencies (OTAs) over hotel brands and airlines.

Hotel booking engine Mirai found a 30% reduction in paid clicks and -36% in direct visits in the EU vs. the U.S. after Google demoted its flights and hotel SERP feature.

In Favoritism, I described how Google gives more visibility to brands in organic search over OTAs and other aggregators. It’s possible that Google is trying to balance traffic to flight and places sites with more brands in the classic organic results.

Users cannot click on map packs in the EUUsers cannot click on Map Packs in the EU. (Image Credit: Kevin Indig)
“Places sites” are the equivalent of hotels to “Flight sites”“Places sites” are the equivalent of hotels to “Flight sites.” (Image Credit: Kevin Indig)

The EU is not the only one that has seen a problem with Google’s SERP features.

First, Yelp filed a lawsuit against Google in 2024 for using SERP features to keep traffic on its site and illegally scraping and using Yelp’s content.

In Augmentation, I presented data and studies showing that SERP features have a net negative effect on clicks.

Second, the FTC reviewed Google’s SERP features but didn’t find them to be a problem in 2013 – a big mistake.

While Google’s prominent display of its own vertical search results on its search results page had the effect in some cases of pushing other results “below the fold”, the evidence suggests that Google’s primary goal in introducing this content was to quickly answer, and better satisfy, its users’ search queries by providing directly relevant information.

2. Shopping

In September, the EU fined Google $2.8 billion for showing price Product Listing Ads (PLAs) above blue links to price comparison sites and demoting price comparison sites in organic search with algorithm updates.

Since then, Google has shown a box with links to price comparison sites for shopping searches, as for hotel and flight searches.

The DMA, which classified PLAs as self-preferencing, came a few months too late for sites like Ladenzeile, Idealo, or Shopalike.

Owner Axel Springer had to shut them down in June after Google Core Updates shot golf ball-sized holes into their armor.

Big shopping retailers like MediaMarkt and Amazon gained the visibility that Ladenzeile & Co. lost in Germany.

3. Default Search Engines

Since March 2024, Google needs to let users in the EU choose a default search engine on Android and Chrome.

It’s a precursor for what’s likely to be a remedy in the current DOJ lawsuit against Google in the U.S.

However, most users still choose Google despite randomized choices for other search engines since the search engine market share distribution in the EU remains unchanged.

The DMA didn’t make a dent in Google’s EU search engine market shareThe DMA didn’t make a dent in Google’s EU search engine market share. (Image Credit: Kevin Indig)
Even when taking Google out of the chart, gains are barely visibleEven when taking Google out of the chart, gains are barely visible. (Image Credit: Kevin Indig)

So far, the impact of the DMA on Google seems minimal or non-existent, and users are getting frustrated with the circumcised SERP experience.

Stable market share in the EU shows that Google has won Search, and antitrust lawsuits are coming too late.

The lawsuits against gatekeepers and resulting remedies are not without controversy, but I don’t see the EU backing down. The DMA will continue to diverge the internet experience in the U.S. and EU, probably to an advantage for EU sites.

Global companies operating in the U.S. and EU can compare the impact of SERP features and AI Overviews to better understand their impact.

You can measure differences in clicks, impressions, and CTR by comparing the same keywords in different countries in the same position. You could already do that today with AI Overviews, for which Google doesn’t really provide any data.

At the same time, it will be interesting to see if Google’s free product listings and AI Overviews will be seen as self-preferencing.

After Google’s transition from a search engine to a shopping marketplace, free and paid shopping grids appeared in regular searches, not just the shopping tab.

I wrote in ecommerce shifts

Just in time for the shopping season, Google made product filters permanent for queries with clear intent after testing the feature for about a year. What used to be the Google Shopping tab is now the default for Search.

Google replayed its boiling frog playbook: habituate users with small features and slowly expand. Google first showed paid listings (PLAs), then organic listings, and now a full product search page.

For merchants and retailers, the new marketplace layout can significantly disrupt organic traffic. Google has highlighted the importance of the Merchant Center for paid and organic listings for a while now, likely to prepare merchants for the coming transformation. Within this change, classic Search is becoming less important and marketplace optimization more important.

It’s possible that Google already expects the DMA to see AI Overviews as a DMA violation, which is why it launched in the UK, India, Japan, Mexico, Brazil, and Indonesia – but not in the EU. They also didn’t roll out in Australia and Canada, where governments try to force Google to pay publishers.

While the EU becomes a tougher market for U.S. tech companies, it might become more attractive for European players, which is the purpose of the DMA.

For companies with an affiliate or ad-revenue business model, the EU could become a refuge where growing SEO traffic is easier.

However, a change in SERP design does not protect sites from losing organic traffic in classic results, as we can see in the example of Idealo and Ladenzeile.


DMA implementation sinks 30% of clicks and bookings on Google Hotel Ads

How the European Commission Is Making Google a Worse Product (Again)


Featured Image: Paulo Bobita/Search Engine Journal



Source link

tech
We will be happy to hear your thoughts

      Leave a reply

      Reflex The Best
      Logo