=== 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 SEO Tip To Get New Site Picked Up Faster – Reflex The Best

Google’s SEO Tip To Get New Site Picked Up Faster


Google’s John Mueller offered a useful for technical SEO tip for those launching a new site that will help your site get picked up by Google faster by avoiding this one common mistake.

High Priority For Site Launch

Launching a website is a chance to take everything learned from previous experiences and apply them with the benefit of hindsight. There’s no better teacher for success than failure because lessons learned from mistakes are never forgotten.

Someone who recently registered a new domain started a discussion on Reddit asking what were the top three considerations for launching a successful website before anything else has been done. The person asking the question preemptively ruled out the obvious answer of adding the domain to Google Search Console and set the ground rule that the niche or type of business didn’t matter. What did matter is that the suggestions must be important for scaling traffic within the first six month of the website.

They asked:

“Let’s say you have a brand new domain and you’ve been given a task to build traffic in the next 6 months. The niche, business does not matter, and the basics like ‘adding domain to Google search console’ don’t matter.

Tell me what are the first 3, high-priority things you’ll implement.”

The Most Upvoted Answer

It’s somewhat surprising that the most upvoted answer, with 83 votes, was one that offered the most obvious suggestions.

The top upvoted answer was:

“Create landing pages/content for your lowest funnel keyword opportunities and work the the way up.”

It’s a matter of course that the information architecture of the site should be planned out ahead of time (things like keywords, topics, key pages, a complete org-chart style map of categories with room left for expanding topical coverage, and an interlinking strategy). The upvoted answer is absolutely correct but it’s also fairly obvious.

The rest of that highly upvoted response:

“Claim brand on top social medias.

Build easiest citations and directories that I know get indexed. Plus niche relevant ones.

Start reactive digital PR as main initial link building campaign.”

The obviousness of that upvoted answer is in contrast with the not so obvious quality of Mueller’s response.

John Mueller Advice On SEO Preparation

John Mueller’s advice is excellent and offers an insight into a technical issue that is easy to overlook.

He wrote:

“Just throwing this out there – if you don’t have a site ready, either keep DNS disabled or put up a custom holding page. Don’t use a generic server / CMS holding page. It generally takes longer for a site that’s known to be parked / duplicate to get recognized as a normal site than it does for a site to be initially picked up.”

Keep DNS Disabled

DNS stands for Domain Name System and is a reference to the backend process of converting a domain name to the IP address where the actual content exists. All content exists at an IP address, not at the domain name. The domain name just points to where the content is. By keeping DNS disabled what happens is that Google doesn’t discover the domain pointing to anything so it essentially doesn’t exist.

Don’t Use Generic Server/CMS Holding Page

A generic server holding page is the same as a parked domain, it’s like a false signal to Google that something exists at the IP address that a domain name resolves to.

The effect of Mueller’s advice regarding disabling a DNS and not using a generic holding page is to keep the domain name from resolving to a holding page (assuming that a registrar’s holding page is also turned off). This keeps Google from sniffing out the domain and finding a generic “nothing here” holding page.

Mueller’s advice points to the technical issue that Google will recognize and index a site faster if a generic version is never activated and the domain name essentially doesn’t exist.

So if you want your website to be picked up and indexed quickly then it’s best to not use a generic domain holding page.

Read Mueller’s advice here:

Brand New Domain : What are the first 3 things you’ll do?

Featured Image by Shutterstock/Luis Molinero



Source link

tech
We will be happy to hear your thoughts

      Leave a reply

      Reflex The Best
      Logo