=== 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 vs. AI — Whiteboard Friday – Reflex The Best

Google vs. AI — Whiteboard Friday


The author’s views are entirely their own (excluding the unlikely event of hypnosis) and may not always reflect the views of Moz.

Large Language Models have taken the world by storm in recent months. In today’s episode, Tom goes over some of the new threats to Google from recent advances in machine learning models like ChatGPT, and how Google might react to those threats.

Click on the whiteboard image above to open a high resolution version in a new tab!

Video Transcription

Happy Friday, Moz fans. Today I want to talk about some of the threats posed to Google by recent advances in large language models and natural language processing and chatbots and this kind of thing.

I want to talk about how Google might react to some of these threats because that’s obviously going to affect us, whatever happens, as SEOs. Now the lens that I want to look at this through is think about some of the different kinds of query that we currently use Google for. Really it’s kind of an artifact of Google’s dominance in the last decade or two that we use Google as the go-to tool for such a varied set of uses.

So I’ve got some example searches here, and obviously this is just some random things that came into my head. This is not representative of everything people use Google for, which is even more varied. But I’ve got like a commercial query, “running shoes £ 50.” So a lot of people know now and the data has been around for a few years that Amazon is actually a bigger product search engine than Google in the U.S.

More product search journeys start on Amazon than on Google. So that’s not anything to do with large language models, but that’s sort of some context to this scenario for Google. Then we’ve got things like “pancake recipe,” sort of very informational, uncontroversial where, yeah, actually a chat AI can do a pretty good job just sort of aggregating all the different recipes that it’s consumed in its training set.

“COVID symptoms” way more authority sensitive query, right? So at the moment, this is kind of a strong point for Google because, weirdly enough, as consumers we trust Google more than we might trust something like an NLP model right now. Then “Moz blog,” so this is your bread- and-butter navigational web search, where really a web search engine, this is what they originally set out to be good at, and they are the sort of natural tool for a problem like this.

Whereas for some of these other ones, it’s not obvious that what I want is a website at all, let alone a web search engine. Now I think the interesting thing here, so I talked about how Amazon was probably the natural competitor for some of these product queries, but it’s a more complex picture than that.

So though Google is trying to compete directly with this threat with things like the product updates, making sure that they are a good product search engine, and if you want to be a bit conspiratorial, you could say, well, maybe they’re trying to make sure that Amazon affiliates aren’t too dominant in the SERPs. It’s also the case that these are big money terms for Google in terms of AdWords.

But like I said before, we’re using Google for everything these days and have done for some time. Part of that is making sure that you’re locked in with these kinds of queries. You get in the habit of using Google. You’re in their ecosystem, so you’re more likely to use them for this kind of thing. Now I’ve written loss leaders here, and I think that’s an interesting concept, an interesting way of thinking about this.

In retail, you might have a loss leader, which would be a product that the store does not make much money on or it might even lose money on, but they’ve got you in, so you’re going to buy the high-margin products as well. So these kinds of query, these are not so obviously easy to monetize, but they can be loss leaders to get us engaged when we do make these high-margin searches.

Now that’s kind of why I’ve included this search here because I want to explain why these searches, which might seem like they are not … something like a chat AI response to this is actually very expensive to produce relative to how easy it is to monetize.

You can kind of see that with how Amazon and Google have both struggled to make money on their sort of home chat devices, Alexa and I think it’s called Google Home. They both sort of struggle to make money on those because these kinds of query are hard to monetize.

But they are loss leaders that will engage you for this kind of thing. So that’s why they’re important. Obviously, for this kind of query, this is the one where Google is most obviously threatened by things like the new Bing and things like ChatGPT and that kind of technology as an alternative to a search engine for now.

So how might they respond to that? Well, obviously, if you can’t beat them, join them. Google is launching Bard. Their original announcement on February 6th and most sort of logical predictions are that, well, suggest that it was going to end up in the SERPs sooner or later.

At the moment, it’s a separate interface to SERPs. But it seems like it will end up looking like a SERP feature sooner or later. Then we should expect to see more and more sort of Knowledge Graph results. At the moment, there are a lot of things you can search for on Google where you won’t see a website as a result. If you search for something like “five liters in gallons,” then you won’t see a website as the top result.

You will see a Knowledge Graph result, and I’d expect that to become more and more common because that is a better answer for these kinds of queries often than showing a website. Now what about COVID symptoms? What about the more authority sensitive query? Well, I’d say the threat here is kind of the other way around. It’s not that Google thinks you might use a chatbot to ask for COVID symptoms, although in time you might.

It’s more that if Google’s own results are not high quality, if Google’s own results were written by AI, then they’ve lost their differentiator, right? At the moment, we trust Google more than we would trust some of these new technologies, more than we would trust some other search engines. They need to maintain that edge, and the way to maintain that edge is by making sure that their results are written by people, at least by authorities or at least checked by authorities.

Whereas some of these alternatives are not. So that’s why you see things like the Helpful Content Update, which now looks extremely prescient, that was late last year, and also core updates. The core updates are Google refining and improving its algorithm over time, but making sure they stay ahead of the game.

Similarly, that goes to these kinds of queries too. They have to make sure they’re still the best at this kind of thing. At the moment, things like Bard and things like the new Bing, the chat interface on new Bing don’t really work for web search. But in time, there’s no reason why they couldn’t. So Google has to maintain an edge in this area as well.

So that was a quick, whistle-stop tour through how I think Google might react to some of these new threats. Let me know what you think on Twitter or on Mastodon or on any other or on LinkedIn or on Facebook. I’d love to hear more people’s opinions about these kinds of emerging trends.

Video transcription by Speechpad.com



Source link

tech
      Reflex The Best
      Logo