How to Use Starter Templates in WordPress to Build Any Site You Need

Starter templates in WordPress are pre-built, fully designed page layouts that you can import into your site in a single click, giving you a complete visual structure — headers, footers, inner pages, typography, and color schemes — without writing a single line of code. They are bundled with themes like Astra, Neve, Kadence, and OceanWP, and are accessed through companion plugins that connect to a library of industry-specific designs.

The practical value is significant: instead of assembling a homepage from scratch, you import a template matched to your niche (SaaS product, law firm, WooCommerce store, portfolio), then replace placeholder content with your own. The entire process from a blank WordPress install to a styled, multi-page site can take under 30 minutes — provided your hosting environment is properly configured.

What You Need Before You Start

Before touching the WordPress dashboard, verify the following server-side prerequisites. Many template import failures trace back to inadequate hosting configuration, not plugin bugs.

Minimum PHP and memory requirements:

• PHP 7.4 or higher (PHP 8.1+ recommended for modern themes)
• memory_limit set to at least 256 MB in php.ini

max_execution_time of 300 seconds or more
upload_max_filesize and post_max_size both at 64 MB or higher

If you are on a VPS Hosting plan, you can edit these values directly in /etc/php/8.1/fpm/php.ini (adjust the version path to match your stack) and reload PHP-FPM:
sudo nano /etc/php/8.1/fpm/php.ini
# Set: memory_limit = 256M, max_execution_time = 300
sudo systemctl reload php8.1-fpm
On shared environments, these limits are often set through the hosting control panel. If you are using a Shared Web Hosting plan, check the PHP configuration section in cPanel or contact support to raise the limits before attempting a full-site import.
SSL is strongly recommended before launch. Importing a template over HTTP and then switching to HTTPS later causes mixed-content issues in embedded images and scripts. Configure your SSL Certificate before running the import.
Step 1: Choose a Theme That Supports Starter Templates
Not every WordPress theme ships with a template library. The following four are the most mature ecosystems, each with hundreds of templates and active development:



Theme
Template Library Size
Page Builder Compatibility
Lightweight Base (KB)
Free Tier








—
—
—
—
—








**Astra**
250+ templates
Elementor, Gutenberg, Beaver Builder, Brizy
~50 KB
Yes








**Neve**
100+ templates
Elementor, Gutenberg, Brizy
~30 KB
Yes








**Kadence**
100+ templates
Gutenberg (native), Elementor
~40 KB
Yes








**OceanWP**
50+ templates
Elementor, Gutenberg
~60 KB
Yes





Astra is the most widely deployed option and has the deepest Elementor integration. Kadence is the strongest choice if you want to stay entirely within the native Gutenberg block editor and avoid a third-party page builder dependency. Neve is the most performance-optimized out of the box.
To install your chosen theme:

Log in to your WordPress dashboard.
Navigate to Appearance > Themes.
Click Add New, search for your theme by name.
Click Install, then Activate.

Step 2: Install the Starter Templates Plugin
Each theme ecosystem uses a slightly different plugin to expose its template library. The table below maps themes to their companion plugins:



Theme
Plugin Name
WordPress.org Slug








—
—
—








Astra
Starter Templates
`astra-sites`








Neve
Neve Pro / Otter Blocks
`otter-blocks`








Kadence
Kadence Starter Templates
`kadence-starter-templates`








OceanWP
Ocean Extra
`ocean-extra`





For Astra (the most common workflow):

Go to Plugins > Add New.
Search for Starter Templates.
Install and activate the plugin named Starter Templates – Elementor, Gutenberg & Beaver Builder Templates.

Once activated, a new menu item appears under Appearance > Starter Templates.
Critical edge case: If you are migrating an existing site and already have content, do not run a full-site import. It will overwrite your existing pages, menus, and widgets. Use Import Single Page or Import Home Template instead, and manually merge the design elements you need.
Step 3: Select and Import a Starter Template
After activating the plugin, the import wizard launches automatically or is accessible via Appearance > Starter Templates.
Workflow:

Choose your page builder. The wizard asks whether you want to use Elementor, Gutenberg, or Beaver Builder. This choice is permanent for the import — you cannot mix builders within a single template import. Choose Gutenberg if you want a leaner, plugin-free setup; choose Elementor if you need advanced drag-and-drop flexibility.


Filter by category. Templates are organized by industry (Business, eCommerce, Agency, Restaurant, Portfolio, Education, etc.). Use the search bar for keyword filtering.


Preview before importing. Click any template thumbnail to open a live preview. Inspect the inner pages (About, Contact, Blog) — not just the homepage — because the homepage often looks polished while inner pages are sparse.


Choose your import scope:


Import Complete Site — imports all pages, posts, menus, widgets, and theme customizer settings. Best for new sites.
Import Home Template — imports only the homepage layout. Best for existing sites where you want to refresh the front page only.


Confirm the import. The plugin will download demo content, images (from Unsplash or the plugin's CDN), and customizer settings. On slower connections or restrictive servers, this can take 60–90 seconds.

What gets imported and what does not:



Asset
Imported
Notes








—
—
—








Page layouts
Yes
All pages in the demo








Demo images
Yes
Placeholder images from Unsplash CDN








Plugins (WooCommerce, etc.)
Prompted
Plugin installer runs as part of the wizard








Your existing posts/pages
No
Existing content is not deleted unless you choose "Delete Previously Imported Data"








Custom domain/DNS settings
No
Must be configured separately








SSL certificate
No
Must be pre-configured





Step 4: Customize the Template
Using the Elementor Editor
Navigate to Pages, hover over any page, and click Edit with Elementor. The visual editor opens with the imported layout fully editable.
Key customization actions:

Replace images: Click any image widget, then click the image thumbnail in the left panel to open the media library. Replace demo images with your own assets.
Edit text inline: Click directly on any text element to edit it in place.
Global Colors and Fonts: In Elementor, go to Site Settings > Global Colors and Global Fonts to define your brand palette and typography system-wide. Changing a global color updates every element that references it across all pages simultaneously.
Section and column structure: Right-click any section to duplicate, delete, or move it. Use the Navigator panel (the layers icon in the bottom toolbar) for complex layouts with nested sections.

After editing, click Update (not Publish — the page is already published; Update saves your changes).
Using the Gutenberg Block Editor
Navigate to Pages, click Edit on the target page. The block editor opens with the imported pattern-based layout.
Key customization actions:

Click any block to select it. Use the toolbar above the block for alignment, color, and formatting options.
Use the List View (the stacked-lines icon in the top toolbar) to see and navigate the full block hierarchy — essential for complex templates with nested Group and Cover blocks.
To change global styles, go to Appearance > Editor > Styles (Full Site Editing themes) or Appearance > Customize (classic themes).
The Styles panel in the Site Editor lets you set global typography and color palettes that cascade across all blocks.

Performance note: Gutenberg-based templates generate cleaner HTML and load faster than Elementor-based ones because they do not require the Elementor runtime JavaScript. For sites where Core Web Vitals are a priority, the Gutenberg path is measurably better.
Step 5: Configure Global Theme Settings
After importing, open Appearance > Customize to fine-tune the global design system. The available panels vary by theme, but all major starter-template themes expose:
Typography:

Set the primary font family for headings (H1–H6) and body text.
Define font sizes, line heights, and letter spacing globally.
Use system fonts (-apple-system, BlinkMacSystemFont, sans-serif) or a Google Fonts selection. System fonts eliminate an external HTTP request and improve LCP scores.

Colors:

Define a primary color (brand accent), secondary color, text color, and background color.
These values populate CSS custom properties (--wp--preset--color--primary) that all imported blocks and widgets reference.

Layout:

Set the global container width (typically 1200px–1440px for modern designs).
Configure header layout: sticky header, transparent header on scroll, mobile menu behavior.
Configure footer columns, widget areas, and copyright text.

Astra-specific: Astra's customizer has a Performance panel where you can disable Google Fonts loading (useful if you are self-hosting fonts for GDPR compliance) and enable CSS minification.
Step 6: Replace Placeholder Content
Template demo content is intentionally generic. Systematic replacement is faster than editing page by page:

Go to Pages and sort by Date to find all pages imported during the template setup.
Open each page and replace:


Headline and body copy with your actual content.
Demo images with your own photos or licensed stock images. Use descriptive alt text for every image.
Placeholder phone numbers, addresses, and email addresses.
Demo navigation links — check Appearance > Menus to ensure all menu items point to real pages.


Update the Site Title and Tagline under Settings > General.
Set your Homepage and Blog page under Settings > Reading.

SEO-critical step: After replacing content, install either Yoast SEO or Rank Math and set a unique meta title and meta description for every page. Template imports do not populate SEO metadata.
Step 7: Extend Functionality with Plugins
Starter templates provide design scaffolding, not functionality. Depending on your site type, you will need additional plugins:



Site Type
Recommended Plugin
Purpose








—
—
—








eCommerce
WooCommerce
Product catalog, cart, checkout








Lead generation
WPForms or Contact Form 7
Contact and inquiry forms








Membership
MemberPress or Restrict Content Pro
Gated content








SEO
Rank Math or Yoast SEO
On-page SEO, sitemaps, schema








Performance
WP Rocket or LiteSpeed Cache
Caching, minification, lazy loading








Security
Wordfence or Solid Security
Firewall, malware scanning








Backup
UpdraftPlus
Automated off-site backups





If you are running WooCommerce, verify that your hosting plan can handle the additional database load. A VPS with cPanel gives you the resource headroom and management interface to handle WooCommerce at scale without the constraints of shared hosting.
Step 8: Preview, Test, and Launch
Before publishing, run through this pre-launch checklist:
Visual QA:

Preview on desktop, tablet, and mobile using the WordPress Customizer's responsive preview or browser DevTools.
Check that no demo images remain on any page.
Verify that all fonts loaded correctly (network throttling in DevTools can reveal font-swap flicker).

Functional testing:

Submit every form and confirm the notification email arrives. Check your Email Hosting configuration if transactional emails are not delivering — WordPress's default wp_mail() relies on PHP's mail() function, which many hosts block. Use an SMTP plugin (WP Mail SMTP, Post SMTP) with authenticated credentials.
Click every navigation link and button. Imported templates sometimes contain hardcoded demo URLs.
Test the checkout flow if WooCommerce is active.

Performance baseline:

Run a PageSpeed Insights test on the homepage. Aim for an LCP under 2.5 seconds and a CLS score below 0.1.
If scores are poor, enable caching, optimize images (convert to WebP), and consider a CDN.

Security:

Ensure HTTPS is enforced site-wide. Verify there are no mixed-content warnings in the browser console.
Change the default WordPress admin username if it is still admin.
Set file permissions: directories at 755, files at 644, and wp-config.php at 600.

Once all checks pass, the site is ready. If it is still under a temporary domain, update the WordPress Address (URL) and Site Address (URL) under Settings > General after pointing your domain. You can register or transfer your domain through Domain Registration if you have not done so already.
Common Pitfalls and How to Avoid Them
Import fails mid-process: Usually caused by PHP memory_limit or max_execution_time being too low. Raise these values as described in the prerequisites section, then retry the import.
Demo images do not load after import: The Starter Templates plugin pulls images from an external CDN. If your server has outbound HTTP restrictions or a firewall blocking external requests, images will not download. Whitelist the plugin's CDN domains or temporarily relax outbound rules during import.
Template looks different from the preview: This almost always means a required plugin (Elementor Pro, a specific add-on) was not installed. The import wizard lists required plugins — install all of them before importing.
Customizer changes do not apply to imported pages: Some Elementor templates use Elementor's own global settings rather than the theme customizer. Changes made in Appearance > Customize will not affect Elementor-controlled elements. Use Elementor > Site Settings for those pages.
Performance regression after import: Full-site imports load all demo plugins and assets. Audit your active plugins post-import and deactivate anything you do not need. Each active plugin adds PHP execution overhead on every page load.
Technical Decision Matrix: Choosing Your Build Path



Scenario
Recommended Path








—
—








New site, no existing content, need speed
Astra + Starter Templates + Elementor, full-site import








Performance-critical site (Core Web Vitals priority)
Kadence + Kadence Starter Templates + Gutenberg only








Existing site, redesign homepage only
Any theme + import single page template








WooCommerce store
Astra or Kadence + WooCommerce-specific template








Developer building for a client
Neve + child theme + selective block imports








Minimal plugin footprint required
Kadence + Gutenberg, no Elementor





Pre-Launch Checklist

PHP memory limit is 256 MB or higher before import
SSL certificate is active and HTTPS is enforced
Full-site import completed on a staging environment first, then pushed to production
All demo placeholder text and images replaced
SEO meta titles and descriptions set on every page
All forms tested with real email delivery confirmed
Navigation menus verified — no dead links or demo URLs
Performance baseline measured with PageSpeed Insights
Caching plugin active and configured
Admin username changed from default admin

• wp-config.php permissions set to 600
• Domain DNS pointing to correct server IP

FAQ

Can I use a starter template on an existing WordPress site without losing my current content?

Yes, but you must select "Import Single Page" or "Import Home Template" rather than "Import Complete Site." The full-site import will overwrite existing pages, menus, and widget areas. Always take a full backup before any import operation.

Do starter templates work with any WordPress theme, or only specific ones?

Starter templates are tied to specific theme ecosystems. The Astra Starter Templates plugin only works with the Astra theme. Kadence Starter Templates require the Kadence theme. You cannot cross-import templates between incompatible themes.

Why do my imported pages look different from the template preview?

The most common cause is a missing required plugin — typically Elementor Pro or a premium add-on. The import wizard lists all required plugins; install every one of them before importing. A secondary cause is a PHP memory limit that caused the import to fail silently, leaving some assets undownloaded.

Will using a starter template hurt my site's SEO?

Not inherently, but starter templates import demo content with no SEO metadata. You must manually set unique meta titles, descriptions, and structured data for every page. Additionally, some Elementor-heavy templates generate bloated HTML that can negatively affect Core Web Vitals — audit with PageSpeed Insights after import.

Can I switch to a different starter template after I have already customized my site?

Technically yes, but it is destructive. Importing a new complete-site template overwrites your existing customizations. The practical approach is to export your current customizer settings (using a theme export tool), import the new template on a staging site, manually migrate your content, then push the staging site to production.