Master Your Content Workflow: A Complete Guide to WordPress Import Export Blog Posts

A modern, split-screen digital workspace. On the left, a WordPress admin dashboard is open to the export tool. On the right, a clean Laravel CMS interface shows imported posts. The mood is efficient, professional, and seamless.

Streamline your content management, migrate between platforms, and safeguard your digital assets with our definitive guide to importing and exporting WordPress blog posts. Whether you're using the native tools or exploring powerful alternatives like WordPress Import Export Lite, this guide provides the actionable insights you need.

Explore Methods Optimize Your Workflow

Choose Your WordPress Import Export Strategy

Different scenarios call for different tools. Our interactive guide helps you select the right approach for migrating, backing up, or restructuring your WordPress blog posts.

Built-In Export/Import

WordPress includes robust native tools under Tools > Export and Tools > Import. These are perfect for standard content transfers between WordPress installations. The process generates an XML file (WXR - WordPress eXtended RSS) containing your posts, pages, comments, custom fields, categories, and tags.

🛠️ Pro-Tip:

Always use the"Download Export File" option for a full backup before any major site change. For large sites, export by content type (e.g., only posts) to manage file size. Remember, the native importer has a 2MB file limit by default, which can be increased via php.ini settings.

While excellent for WordPress-to-WordPress moves, this XML format is not natively compatible with other CMS platforms. This limitation is a primary driver for businesses seeking more flexible solutions, leading many to explore WordPress to Laravel migration paths for greater control and scalability.

Extending Functionality with Plugins

Plugins like WordPress Import Export Lite, All-in-One WP Migration, and Duplicator fill the gaps left by native tools. They offer user-friendly interfaces, support for larger files, incremental exports, and scheduling.

WordPress Import Export Lite: A free plugin ideal for beginners. It allows filtering by date, author, or status before export and provides a clear CSV option for data manipulation in spreadsheets.
Advanced Features: Premium plugins often include multisite support, cloud storage integration (Dropbox, Google Drive), and the ability to exclude specific file types or database tables.
Limitations: Plugin conflicts can arise, especially during import. Performance on sites with tens of thousands of posts can degrade. Furthermore, they remain locked within the WordPress ecosystem, a challenge for those considering a Laravel CMS like WordPress for future growth.

Beyond WordPress: Platform Migration

For enterprises and developers, the goal often isn't just moving posts between WordPress sites, but liberating content from WordPress entirely. This involves converting WordPress export data into formats usable by modern frameworks like Laravel.

Tools like Waravel specialize in this advanced user migration, parsing the WordPress WXR file and transforming posts, meta-data, images, and even SEO structures into a Laravel application. This process, detailed in our guide "How To Migrate Your Entire WordPress Site To Laravel...", ensures zero data loss while unlocking superior performance and security.

Core Benefits of Mastering WordPress Import Export

Understanding these processes is more than a technical skill—it's a strategic business advantage for content managers, developers, and agency owners.

🛡️

Robust Content Backup & Disaster Recovery

Regular exports are your ultimate safety net. A scheduled export strategy protects against hacking, server failures, or accidental deletion. Combine this with a structured strategic brand building plan, and your core content assets remain secure, preserving your brand's digital voice and authority.

🚀

Seamless Platform Migration & Modernization

Export is the first step in leaving WordPress limitations behind. Migrating to a high-performance Laravel platform, as facilitated by our WordPress Migration Tool, allows for advanced customization, better performance optimisation, and a developer-friendly environment, ultimately driving business growth.

🔄

Efficient Content Syndication & Multi-Site Management

For agencies or publishers managing multiple sites, exporting posts from a master site and importing to client sites streamlines content distribution. This workflow ensures brand consistency and can be partially automated, freeing up resources to focus on core features that set your service apart.

Step-by-Step: Advanced Import Export Techniques

Handling Complex Data & Media

A simple post export might capture text and categories, but modern blogs are rich with featured images, galleries, embedded videos, custom post meta, and complex ACF (Advanced Custom Fields) data. The standard export includes attachments, but often only as references.

For a truly complete migration—especially when moving to a different architecture like Laravel—you need a tool that doesn't just list images but fetches and reassigns them. This is where specialized services excel, ensuring your visual brand building assets remain intact.

⚙️ Expert Insight:

Before any major export, audit your site's media library. Use plugins to find orphaned attachments. During import to a new platform like Laravel, consider using a CDN from the start. This not only improves load times but also decouples media from your database, a key principle in modern performance optimisation.

Checklist: Pre-Export Audit

✓ Clean Database: Delete spam comments, post revisions, and transient options.
✓ Update Permalinks: Ensure your permalink structure is consistent and SEO-friendly.
✓ Check Shortcodes: Note any custom shortcodes that may not translate to the new platform.
✓ Document Custom Functionality: Any PHP snippets in themes/plugins that affect post display need migration planning.

The SEO Imperative During Migration

The most critical aspect of moving WordPress Import Export Blog Posts is preserving search engine rankings. A clumsy export/import can break URLs, lose meta titles/descriptions, and corrupt alt text.

Professional migration tools go beyond content. They map old URLs to new ones, automatically implement 301 redirects, and ensure all Yoast SEO or Rank Math meta-data is carried over. This level of detail is what makes a service like Waravel's automated migration indispensable for businesses, as highlighted in our case studies on maintained and improved SEO post-migration.

Ready to Scale?

If managing WordPress exports feels limiting, it's time to consider a platform built for growth.

Unlock The Power Of Laravel

Frequently Asked Questions: WordPress Import Export Blog Posts

Get instant answers to the most common and complex questions about managing your WordPress content.

The native WordPress export is a core feature that creates a comprehensive WXR (XML) file. It's reliable but basic, with limited filtering options and a strict file size limit. WordPress Import Export Lite is a free plugin that builds on this foundation. It offers a more user-friendly interface, the ability to filter posts by date, status, or author before exporting, and can export to CSV format for easy spreadsheet editing. For advanced filtering, scheduling, and large site handling, the premium version of such plugins is recommended.

Yes, absolutely. This is a growing trend for businesses seeking more scalable and secure solutions. The process involves using your WordPress export file (WXR) as the source. However, a direct import into Laravel isn't possible without a conversion tool. Specialized platforms like Waravel are designed precisely for this. They parse the WordPress XML, transform the data into Laravel models and migrations, transfer all media, and crucially, preserve your SEO structure. This allows you to migrate WordPress to Laravel effortlessly.

This common error stems from PHP's file upload limits. Solutions include:

Increase PHP Limits: Modify your php.ini file: upload_max_filesize = 256M and post_max_size = 256M.
Use a Plugin: Migrate to a plugin like All-in-One WP Migration or Duplicator, which split large files.
Manual SQL Import: For developers, you can export the database directly via phpMyAdmin and import it, bypassing the WordPress importer.
Use a Professional Service: For massive, complex sites, consider an automated service that handles the heavy lifting server-side, avoiding browser-based import limits altogether.

The standard WXR export file includes taxonomy data (categories, tags) and author information. During a standard WordPress-to-WordPress import, you'll be given options:"Import author" (assign to existing users or create new ones) and"Download and import file attachments". Ensure these are checked. For migrations to other systems like Laravel, the success depends on the migration tool's logic. High-quality tools will create the corresponding Eloquent models for categories and tags, map old author IDs to new user IDs, and maintain all relationships, ensuring your content organization remains intact. Reviewing a Laravel CMS comparison can help you choose a platform with robust import capabilities.

Ready to Transform Your Content Management?

Mastering WordPress Import Export Blog Posts is just the beginning. If you're constrained by WordPress's limitations, scaling challenges, or security concerns, it's time to explore a modern, powerful alternative. Leverage a Laravel-based platform designed for performance, security, and developer joy.

Hire a Laravel Migration Expert Today Schedule a Consultation

Learn more about our vision and commitment on our About Us page, or explore our comprehensive WordPress Tools suite.

Choosing Your Tool: A Detailed Decision Matrix

Selecting the right import/export method depends on multiple factors. This matrix goes beyond basic features to help you weigh long-term implications, especially when considering platform evolution.

Scenario / Requirement	Recommended Tool/Method	Technical Complexity	Long-Term Strategic Value
Simple blog backup for a small site (< 100 posts)	Native WordPress Export	Low	Adequate for basic archiving, but offers no path for platform evolution. Ideal for hobbyists.
Migrating a large e-commerce site with custom fields & orders	Premium Plugin Suite (e.g., WP All Export Pro + WooCommerce add-ons)	Medium-High	Maintains WooCommerce structure within WordPress. Complex but keeps you within a potentially limiting ecosystem for high-scale transactions.
Enterprise content decoupling: Moving to a headless CMS or Jamstack architecture	Custom API Development + Export Parsing	Very High	Maximizes flexibility and performance. Requires significant developer resources but future-proofs your content delivery across any front-end.
Agency managing 50+ client sites needing standardized content updates	Scheduled CSV Exports/Imports via WordPress Import Export Lite + Custom Scripts	Medium	Good for operational efficiency but scales linearly with workload. A centralized Laravel-based content hub could offer non-linear efficiency gains.

📈 Strategic Takeaway:

If your WordPress Import Export Blog Posts workflow feels like a recurring tactical task rather than a strategic asset, it's a sign your underlying platform may be the constraint. The highest long-term value often lies in migrating to a system where content is truly portable and API-first, reducing your future dependence on any single import/export tool.

Case Study: Migrating a 10,000-Post Editorial Site

The Challenge: Performance & Editorial Workflow Breakdown

A major digital publisher was experiencing severe slowdowns in the WordPress admin panel. Simple actions like searching posts or loading the editor took 10-15 seconds. Their native export would time out, and even premium plugins struggled with the volume of posts, custom taxonomies (they had over 200 niche categories), and a 50GB media library. Their editorial calendar was constantly disrupted.

The initial instinct was to upgrade hosting—a costly recurring expense. Instead, they analyzed the root cause: a database bloated with post revisions, transient options, and inefficient plugin queries. A standard export would carry this bloat forward.

The Solution: A Two-Phase Migration

Data Purification & Export: They used a combination of WP-CLI commands to strip out unnecessary data (e.g., wp post delete $(wp post list --post_type='revision' --format=ids)) and a custom script to generate a clean WXR file, segmented by year.
Platform Transition: They used an automated migration service to ingest the segmented WXR files. The service didn't just import posts; it transformed the data into an optimized Laravel structure with a dedicated search index (using Laravel Scout) and cloud-hosted media. The new editorial interface was built with Livewire, providing real-time updates.

Results Achieved

⚡ Admin Panel Load Times: Reduced from 12s to < 300ms.
📈 SEO Traffic: Maintained 100% of organic visibility; saw 15% growth in 6 months due to improved site speed.
💰 Hosting Costs: Reduced by 60% by moving to a more efficient stack.
🛠️ Developer Onboarding: New features could be implemented weeks faster in the clean Laravel codebase.

This case illustrates that a complex WordPress Import Export Blog Posts project is often the catalyst for a holistic performance and workflow transformation, not just a data transfer.

Under the Hood: Anatomy of a WordPress Export (WXR) File

Understanding the XML structure empowers you to manipulate exports for custom needs and troubleshoot failed imports.

Key XML Nodes and Their Meaning

(The Core Post Object)

Each post, page, or custom post type is an . Critical child nodes include:

</code>: The post title.</li> <li><code><content:encoded></code>: The full HTML post content.</li> <li><code><wp:post_id></code>: The original ID. Crucial for maintaining internal links.</li> <li><code><wp:post_type></code>: Identifies 'post', 'page', 'attachment', etc.</li> <li><code><category></code>: Contains taxonomy assignments with nicename and domain (e.g., 'category' vs 'post_tag').</li> </ul> </div> <div class="bg-slate-800 p-6 rounded-xl text-white text-white"> <h4 class="text-xl font-bold mb-2 text-amber-400"><wp:postmeta> (The Hidden Data)</h4> <p class="text-slate-300">This is where plugins store everything: SEO meta from Yoast, custom fields from ACF, featured image IDs, and more. A single post can have dozens of <code><wp:postmeta></code> entries. During a platform migration, correctly interpreting these key-value pairs is the most complex part of the process.</p> </div> </div> </div> <div> <h3 class="text-2xl font-bold mb-6">Common Pitfalls & How to Solve Them</h3> <div class="space-y-6"> <div class="bg-slate-800 p-6 rounded-xl text-white text-white"> <h4 class="text-xl font-bold mb-2 text-amber-400">CDN or Offloaded Media URLs</h4> <p class="text-slate-300">If you use a CDN (like BunnyCDN) or an offload plugin (like WP Offload Media), your export file may contain the CDN URL (e.g., <code>https://cdn.yoursite.com/image.jpg</code>) instead of the local WordPress path. On import to a new site, these links will break. <strong style="color: inherit;">Solution:</strong> Before export, use a search-and-replace plugin to temporarily revert URLs to the local domain, or ensure your migration tool has a URL rewriting engine.</p> </div> <div class="bg-slate-800 p-6 rounded-xl text-white text-white"> <h4 class="text-xl font-bold mb-2 text-amber-400">Serialized Data in Post Meta</h4> <p class="text-slate-300">WordPress serializes arrays and objects (like ACF repeater field data) for storage. A naive find/replace on the XML file can corrupt this serialized data because the string length is stored within it. <strong style="color: inherit;">Solution:</strong> Use dedicated search/replace tools like"Better Search Replace" that handle serialization, or rely on migration tools that process the data programmatically, respecting the serialization format.</p> </div> <div class="bg-slate-800 p-6 rounded-xl text-white text-white"> <h4 class="text-xl font-bold mb-2 text-amber-400">Missing Author Mapping Due to Email Conflict</h4> <p class="text-slate-300">If you're importing to a site where an author email already exists but is assigned to a different user ID, the import can assign posts to the wrong person. <strong style="color: inherit;">Solution:</strong> During the import process, carefully use the"Import author" mapping screen, or pre-clean your user data in the source site to ensure emails are unique and match the target site's desired structure.</p> </div> </div> </div> </div> </div> </section>  <section class="py-16 px-4 md:px-12 lg:px-24 bg-gradient-to-br from-slate-50 to-amber-50"> <div class="container mx-auto max-w-6xl"> <h2 class="text-3xl md:text-4xl font-bold mb-8 text-center text-slate-900">Beyond the Export: Future-Proofing Your Content Strategy</h2> <p class="text-xl text-slate-700 mb-12 text-center max-w-3xl mx-auto leading-relaxed">The ultimate goal isn't to become an expert at exporting, but to architect a content workflow where exports become rare events because your content is inherently portable and platform-agnostic.</p> <div class="grid grid-cols-1 md:grid-cols-2 gap-8"> <div class="bg-white p-8 rounded-2xl shadow-lg border border-slate-200 text-slate-900 text-slate-900"> <div class="w-14 h-14 bg-blue-100 rounded-xl flex items-center justify-center mb-6 text-slate-900 text-slate-900"> <span class="text-3xl">📤</span> </div> <h3 class="text-2xl font-bold mb-4 text-slate-900">Adopt an API-First Mindset</h3> <p class="text-lg text-slate-700 mb-4 leading-relaxed">Instead of viewing your site as a database with a front-end, treat it as a content repository with an API (like the WordPress REST API or a headless GraphQL endpoint). This paradigm shift means your content is <em>always</em> exportable and consumable by any front-end: a mobile app, a static site generator, or a digital kiosk.</p> <p class="text-lg text-slate-700 leading-relaxed">Tools that facilitate <strong style="color: inherit;">WordPress Import Export Blog Posts</strong> are often moving data from one monolith to another. An API-first approach turns your content into a dynamic, flowing asset. Platforms like Laravel with built-in API resources make this the default mode of operation.</p> </div> <div class="bg-white p-8 rounded-2xl shadow-lg border border-slate-200 text-slate-900 text-slate-900"> <div class="w-14 h-14 bg-green-100 rounded-xl flex items-center justify-center mb-6 text-slate-900 text-slate-900"> <span class="text-3xl">🧱</span> </div> <h3 class="text-2xl font-bold mb-4 text-slate-900">Implement Structured Content Models</h3> <p class="text-lg text-slate-700 mb-4 leading-relaxed">WordPress's flexible post meta is both a blessing and a curse. Future-proof by defining strict content models. For example, a"Case Study" post type should have defined fields for Client Name, Challenge, Solution, and Results—not just free-form HTML.</p> <p class="text-lg text-slate-700 leading-relaxed">When content is structured, exporting and importing becomes a matter of mapping fields, not parsing unpredictable HTML. This makes migrations to any system (Craft CMS, Sanity, Laravel Nova) dramatically simpler and more reliable. It elevates your content from mere text to structured data that can be analyzed, repurposed, and seamlessly integrated into new digital experiences.</p> </div> </div> <div class="mt-12 text-center"> <p class="text-2xl font-bold text-slate-900 mb-6">The most powerful export is the one you never have to do again.</p> <a href="https://waravel.com/unlock-the-power-of-laravel" class="inline-block bg-slate-900 hover:bg-slate-800 text-white font-bold py-4 px-8 rounded-xl text-lg shadow-xl transition duration-300 transform hover:scale-105 text-white text-white"> Build Your Future-Proof Foundation </a> </div> </div> </section> <style> /* Fix Tailwind Typography (prose) overriding dark background text colors */ .prose .bg-slate-800 :where(h1, h2, h3, h4, h5, h6, strong, p, li), .prose .bg-slate-900 :where(h1, h2, h3, h4, h5, h6, strong, p, li), .prose .bg-blue-900 :where(h1, h2, h3, h4, h5, h6, strong, p, li), .prose .text-white :where(h1, h2, h3, h4, h5, h6, strong, p, li) { color: inherit !important; } </style>  <div class="mt-8 pt-6 border-t border-gray-200"> <div class="tag-widget"> <h3 class="text-lg font-semibold text-gray-900 mb-3">Tags</h3> <div class="flex flex-wrap gap-2"> <a href="https://waravel.com/tag/wordpress-import-export-blog-posts" class="inline-flex items-center px-3 py-1 rounded-full text-sm font-medium bg-gray-100 text-gray-700 hover:bg-orange-100 hover:text-orange-700 transition-colors duration-200"> <svg class="w-4 h-4 mr-1" fill="none" stroke="currentColor" viewBox="0 0 24 24"> <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M7 7h.01M7 3h5c.512 0 1.024.195 1.414.586l7 7a2 2 0 010 2.828l-7 7a2 2 0 01-2.828 0l-7-7A1.994 1.994 0 013 12V7a4 4 0 014-4z"></path> </svg> Wordpress Import Export Blog Posts </a> <a href="https://waravel.com/tag/wordpress-import-export-lite" class="inline-flex items-center px-3 py-1 rounded-full text-sm font-medium bg-gray-100 text-gray-700 hover:bg-orange-100 hover:text-orange-700 transition-colors duration-200"> <svg class="w-4 h-4 mr-1" fill="none" stroke="currentColor" viewBox="0 0 24 24"> <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M7 7h.01M7 3h5c.512 0 1.024.195 1.414.586l7 7a2 2 0 010 2.828l-7 7a2 2 0 01-2.828 0l-7-7A1.994 1.994 0 013 12V7a4 4 0 014-4z"></path> </svg> Wordpress Import Export Lite </a> </div> </div> </div> </article> </div> </div> </main> <script> document.addEventListener('DOMContentLoaded', function() { const iframes = document.getElementsByTagName('iframe'); Array.from(iframes).forEach(iframe => { iframe.removeAttribute('sandbox'); if (!iframe.hasAttribute('style')) { iframe.style.width = '100%'; iframe.style.maxWidth = '100%'; } }); // Updated selector to match new class const contentDivs = document.querySelectorAll('.wv-content > div'); contentDivs.forEach(div => { if (div.scrollWidth > div.clientWidth) { div.style.wordWrap = 'break-word'; div.style.overflowWrap = 'break-word'; div.style.whiteSpace = 'normal'; } }); }); </script> </main> <div class="waravel-page-rating-container" id="waravel-rating-b67fa85ce4c59b7bf9cefe6e0a92b224"> <div class="rating-header"> <span class="rating-average" style="color: #ffd700">5.0</span> <span class="rating-count">out of 5 (1 rating)</span> </div> <div class="rating-stars" data-url="https://waravel.com/wordpress-tools/ultimate-guide-to-import-export-blog-posts-in-wordpress"> <svg class="rating-star" data-value="1" viewBox="0 0 24 24" width="32" height="32" xmlns="http://www.w3.org/2000/svg"> <defs> <linearGradient id="grad-1-b67fa85ce4c59b7bf9cefe6e0a92b224" x1="0%" y1="0%" x2="100%" y2="0%"> <stop offset="100%" stop-color="#ffd700" /> <stop offset="100%" stop-color="#e0e0e0" /> </linearGradient> </defs> <path d="M12 17.27L18.18 21l-1.64-7.03L22 9.24l-7.19-.61L12 2 9.19 8.63 2 9.24l5.46 4.73L5.82 21z" fill="url(#grad-1-b67fa85ce4c59b7bf9cefe6e0a92b224)" stroke="#ffd700" stroke-width="1"/> </svg> <svg class="rating-star" data-value="2" viewBox="0 0 24 24" width="32" height="32" xmlns="http://www.w3.org/2000/svg"> <defs> <linearGradient id="grad-2-b67fa85ce4c59b7bf9cefe6e0a92b224" x1="0%" y1="0%" x2="100%" y2="0%"> <stop offset="100%" stop-color="#ffd700" /> <stop offset="100%" stop-color="#e0e0e0" /> </linearGradient> </defs> <path d="M12 17.27L18.18 21l-1.64-7.03L22 9.24l-7.19-.61L12 2 9.19 8.63 2 9.24l5.46 4.73L5.82 21z" fill="url(#grad-2-b67fa85ce4c59b7bf9cefe6e0a92b224)" stroke="#ffd700" stroke-width="1"/> </svg> <svg class="rating-star" data-value="3" viewBox="0 0 24 24" width="32" height="32" xmlns="http://www.w3.org/2000/svg"> <defs> <linearGradient id="grad-3-b67fa85ce4c59b7bf9cefe6e0a92b224" x1="0%" y1="0%" x2="100%" y2="0%"> <stop offset="100%" stop-color="#ffd700" /> <stop offset="100%" stop-color="#e0e0e0" /> </linearGradient> </defs> <path d="M12 17.27L18.18 21l-1.64-7.03L22 9.24l-7.19-.61L12 2 9.19 8.63 2 9.24l5.46 4.73L5.82 21z" fill="url(#grad-3-b67fa85ce4c59b7bf9cefe6e0a92b224)" stroke="#ffd700" stroke-width="1"/> </svg> <svg class="rating-star" data-value="4" viewBox="0 0 24 24" width="32" height="32" xmlns="http://www.w3.org/2000/svg"> <defs> <linearGradient id="grad-4-b67fa85ce4c59b7bf9cefe6e0a92b224" x1="0%" y1="0%" x2="100%" y2="0%"> <stop offset="100%" stop-color="#ffd700" /> <stop offset="100%" stop-color="#e0e0e0" /> </linearGradient> </defs> <path d="M12 17.27L18.18 21l-1.64-7.03L22 9.24l-7.19-.61L12 2 9.19 8.63 2 9.24l5.46 4.73L5.82 21z" fill="url(#grad-4-b67fa85ce4c59b7bf9cefe6e0a92b224)" stroke="#ffd700" stroke-width="1"/> </svg> <svg class="rating-star" data-value="5" viewBox="0 0 24 24" width="32" height="32" xmlns="http://www.w3.org/2000/svg"> <defs> <linearGradient id="grad-5-b67fa85ce4c59b7bf9cefe6e0a92b224" x1="0%" y1="0%" x2="100%" y2="0%"> <stop offset="100%" stop-color="#ffd700" /> <stop offset="100%" stop-color="#e0e0e0" /> </linearGradient> </defs> <path d="M12 17.27L18.18 21l-1.64-7.03L22 9.24l-7.19-.61L12 2 9.19 8.63 2 9.24l5.46 4.73L5.82 21z" fill="url(#grad-5-b67fa85ce4c59b7bf9cefe6e0a92b224)" stroke="#ffd700" stroke-width="1"/> </svg> </div> <div class="rating-message" style="display: none; margin-top: 5px; font-size: 14px; color: #4CAF50;"></div> <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Product", "@id": "https://waravel.com/wordpress-tools/ultimate-guide-to-import-export-blog-posts-in-wordpress#webpage", "name": "Ultimate Guide to Import Export Blog Posts in WordPress", "aggregateRating": { "@type": "AggregateRating", "ratingValue": "5", "bestRating": "5", "worstRating": "1", "ratingCount": "1" } } </script> <style> .waravel-page-rating-container { margin: 30px 0; padding: 20px; background: #fdfdfd; border-radius: 8px; box-shadow: 0 2px 10px rgba(0,0,0,0.05); text-align: center; font-family: inherit; } .rating-header { margin-bottom: 10px; } .rating-average { font-size: 24px; font-weight: bold; } .rating-count { font-size: 14px; color: #777; margin-left: 5px; } .rating-stars { display: inline-flex; gap: 5px; cursor: pointer; } .rating-star { transition: transform 0.2s; } .rating-star:hover { transform: scale(1.1); } /* JS Hover States */ .rating-star.hover-active path { fill: #ffd700 !important; } .rating-star.hover-inactive path { fill: #e0e0e0 !important; } </style> <script> document.addEventListener('DOMContentLoaded', function() { const container = document.getElementById('waravel-rating-b67fa85ce4c59b7bf9cefe6e0a92b224'); if (!container) return; const stars = container.querySelectorAll('.rating-star'); const messageDiv = container.querySelector('.rating-message'); const url = container.querySelector('.rating-stars').getAttribute('data-url'); let isVoting = false; stars.forEach((star, index) => { star.addEventListener('mouseenter', () => { stars.forEach((s, i) => { if (i <= index) { s.classList.add('hover-active'); s.classList.remove('hover-inactive'); } else { s.classList.add('hover-inactive'); s.classList.remove('hover-active'); } }); }); star.addEventListener('mouseleave', () => { stars.forEach(s => { s.classList.remove('hover-active', 'hover-inactive'); }); }); star.addEventListener('click', () => { if (isVoting) return; isVoting = true; const rating = star.getAttribute('data-value'); messageDiv.style.display = 'block'; messageDiv.style.color = '#555'; messageDiv.innerText = 'Submitting rating...'; fetch('/api/page-rating/submit', { method: 'POST', headers: { 'Content-Type': 'application/json', 'X-CSRF-TOKEN': '40YvF1VILgp0tUzSduSljKMyg3iLig37n5HfyEpx' }, body: JSON.stringify({ page_url: url, rating: rating }) }) .then(response => response.json()) .then(data => { isVoting = false; if (data.success) { messageDiv.style.color = '#4CAF50'; messageDiv.innerText = 'Thank you for rating!'; setTimeout(() => { location.reload(); }, 1500); } else { messageDiv.style.color = '#F44336'; messageDiv.innerText = data.message || 'Error submitting rating.'; } }) .catch(err => { isVoting = false; messageDiv.style.color = '#F44336'; messageDiv.innerText = 'Network error. Please try again.'; }); }); }); }); </script> </div> <footer class="border-t border-white/5 mt-20"> <div class="max-w-7xl mx-auto px-6 py-16"> <div class="grid grid-cols-1 sm:grid-cols-2 lg:grid-cols-4 gap-10 lg:gap-12">  <div class="sm:col-span-2 lg:col-span-1"> <a href="https://waravel.com" target="_blank" rel="noopener noreferrer" class="flex items-center gap-2 group mb-4"> <div class="w-8 h-8 rounded bg-gradient-to-br from-amber-300 to-amber-600 flex items-center justify-center text-black font-bold text-xl">W</div> <span class="font-bold text-xl tracking-tight group-hover:text-white transition">Waravel</span> </a> <p class="text-sm text-gray-500 leading-relaxed mb-5">The modern CMS built on Laravel. Design, build, and launch beautiful websites — effortlessly.</p> <div class="flex items-center gap-3"> <a href="https://github.com/waravel" target="_blank" rel="noopener noreferrer" class="w-9 h-9 rounded-lg border border-white/10 flex items-center justify-center text-gray-500 hover:text-white hover:border-white/20 transition"> <svg class="w-4 h-4" fill="currentColor" viewBox="0 0 24 24"><path d="M12 0C5.37 0 0 5.37 0 12c0 5.31 3.435 9.795 8.205 11.385.6.105.825-.255.825-.57 0-.285-.015-1.23-.015-2.235-3.015.555-3.795-.735-4.035-1.41-.135-.345-.72-1.41-1.23-1.695-.42-.225-1.02-.78-.015-.795.945-.015 1.62.87 1.845 1.23 1.08 1.815 2.805 1.305 3.495.99.105-.78.42-1.305.765-1.605-2.67-.3-5.46-1.335-5.46-5.925 0-1.305.465-2.385 1.23-3.225-.12-.3-.54-1.53.12-3.18 0 0 1.005-.315 3.3 1.23.96-.27 1.98-.405 3-.405s2.04.135 3 .405c2.295-1.56 3.3-1.23 3.3-1.23.66 1.65.24 2.88.12 3.18.765.84 1.23 1.905 1.23 3.225 0 4.605-2.805 5.625-5.475 5.925.435.375.81 1.095.81 2.22 0 1.605-.015 2.895-.015 3.3 0 .315.225.69.825.57A12.02 12.02 0 0024 12c0-6.63-5.37-12-12-12z"/></svg> </a> <a href="https://x.com/waravel" target="_blank" rel="noopener noreferrer" class="w-9 h-9 rounded-lg border border-white/10 flex items-center justify-center text-gray-500 hover:text-white hover:border-white/20 transition"> <svg class="w-4 h-4" fill="currentColor" viewBox="0 0 24 24"><path d="M18.244 2.25h3.308l-7.227 8.26 8.502 11.24H16.17l-5.214-6.817L4.99 21.75H1.68l7.73-8.835L1.254 2.25H8.08l4.713 6.231zm-1.161 17.52h1.833L7.084 4.126H5.117z"/></svg> </a> </div> </div>  <div> <h4 class="text-white font-semibold text-sm uppercase tracking-wider mb-4">Product</h4> <ul class="space-y-3"> <li><a href="https://waravel.com#features" target="_blank" rel="noopener noreferrer" class="text-sm text-gray-500 hover:text-white transition">Features</a></li> <li><a href="https://portal.waravel.com/pricing" target="_blank" rel="noopener noreferrer" class="text-sm text-gray-500 hover:text-white transition">Pricing</a></li>    </ul> </div>  <div> <h4 class="text-white font-semibold text-sm uppercase tracking-wider mb-4">Resources</h4> <ul class="space-y-3"> <li><a href="https://packages.waravel.com/docs/" target="_blank" rel="noopener noreferrer" class="text-sm text-gray-500 hover:text-white transition">Documentation</a></li> <li><a href="https://community.waravel.com/" target="_blank" rel="noopener noreferrer" class="text-sm text-gray-500 hover:text-white transition">Community</a></li> <li><a href="https://portal.waravel.com/support" target="_blank" rel="noopener noreferrer" class="text-sm text-gray-500 hover:text-white transition">Support</a></li>   </ul> </div>  <div> <h4 class="text-white font-semibold text-sm uppercase tracking-wider mb-4">Company</h4> <ul class="space-y-3"> <li><a href="https://waravel.com/about-us" target="_blank" rel="noopener noreferrer" class="text-sm text-gray-500 hover:text-white transition">About Us</a></li> <li><a href="https://waravel.com/contact-us" target="_blank" rel="noopener noreferrer" class="text-sm text-gray-500 hover:text-white transition">Contact Us</a></li> <li><a href="https://waravel.com/privacy-policy" target="_blank" rel="noopener noreferrer" class="text-sm text-gray-500 hover:text-white transition">Privacy Policy</a></li> <li><a href="https://waravel.com/terms-of-service" target="_blank" rel="noopener noreferrer" class="text-sm text-gray-500 hover:text-white transition">Terms of Service</a></li> </ul> </div> </div>  <div class="mt-12 pt-8 border-t border-white/5 flex flex-col sm:flex-row items-center justify-between gap-4"> <p style="font-size: 0.85em; color: #666; margin-top: 5px;"> <strong>Waravel</strong> is a product owned and operated by <strong>Workers Direct LTD</strong>. <br> Registered Address: 344-348 High Road, Ilford, IG1 1QP, United Kingdom. </p> <p class="text-sm text-gray-600">Built with <span class="text-amber-500">♥</span> using Waravel</p> </div> </div> </footer> </body> </html>

Ultimate Guide to Import Export Blog Posts in WordPress