Essential WordPress Settings After Installation

A new WordPress installation works immediately, but its default configuration should not be treated as a finished website setup.

Review the following settings before building large amounts of content or allowing the website to be indexed.

Create a Backup and Confirm the Environment

Before making structural changes, confirm whether you are working on development, staging or production.

Create a current backup if the environment already contains valuable data.

Record:

• Website URL.
• WordPress version.
• PHP version.
• Active theme.
• Active plugins.
• Hosting and backup access.

General Settings

Open Settings → General.

Site Title

Set the official name of the website or organization.

Themes and plugins may display it in headers, metadata, feeds, email or browser contexts.

Tagline

Replace the default tagline. Use a meaningful description or leave it empty if the theme and SEO configuration do not need it.

WordPress Address and Site Address

These values control where WordPress files are located and where the public website is available.

They are often identical. Do not change them casually; an incorrect value can make the website inaccessible.

Administration Email

Use an address that is monitored and controlled by the organization.

WordPress sends important notifications to this address. A change may require confirmation.

Membership and Default Role

Disable open registration unless the website requires it.

When registration is enabled, use the lowest appropriate default role. Subscriber is safer than a role with publishing permissions.

Language, Time Zone and Date Formats

Set the site language and an appropriate named time zone.

A named city time zone is usually preferable to a fixed UTC offset because daylight saving changes can be handled correctly.

Time configuration affects scheduled posts, events, logs and integrations.

Reading Settings

Open Settings → Reading.

Homepage Display

Choose whether the front page displays latest posts or a selected static page.

For a business or structured website, a static front page is common. You can also assign a separate page as the posts index.

Posts Per Page

Set a suitable number for blog and archive pagination. Themes and custom queries may use their own values.

Feed Settings

Decide how many items feeds include and whether full content or summaries are exposed.

Search Engine Visibility

During development, you may request that search engines avoid indexing the site.

This setting is not privacy protection. Use authentication or access restrictions for private environments.

Before launch, confirm that the setting is disabled and verify the website’s actual robots directives.

Writing Settings

Open Settings → Writing.

Review:

• Default post category.
• Default post format where supported.
• Other publishing integrations provided by plugins.

Avoid leaving important content in an unsuitable default category such as “Uncategorized.” Rename or replace it before publishing.

Discussion Settings

Open Settings → Discussion.

Decide whether the website needs comments.

If comments are enabled, review:

• Default comment permissions.
• Comment moderation.
• Notification emails.
• Author requirements.
• Automatic closing of old discussions.
• Avatars.
• Spam protection.

Comments create moderation, privacy and spam responsibilities. Disable them where they do not support the website’s purpose.

Media Settings

Open Settings → Media.

WordPress can generate several image sizes when files are uploaded.

Review thumbnail, medium and large dimensions according to the theme and content strategy.

Changing sizes does not automatically regenerate older image files. That may require a separate process.

Avoid creating many unnecessary image variants through themes and plugins, especially on media-heavy websites.

Permalink Settings

Open Settings → Permalinks.

Choose a stable, readable URL structure before publishing.

A common structure is based on the post name, but the best choice depends on the website.

Consider:

• Existing URLs during a migration.
• News or date-based publishing needs.
• Content type archives.
• Multilingual paths.
• Future stability.

Changing permalink structures after indexation requires redirects and careful testing.

Saving the Permalinks screen also refreshes WordPress rewrite rules, which can resolve some 404 problems.

Privacy Settings

Open Settings → Privacy.

Select or create the website’s privacy policy page.

WordPress provides tools and suggested text, but the final policy must reflect the website’s real data processing and applicable legal requirements.

Do not publish generic text without reviewing forms, analytics, cookies, ecommerce, external services and retention practices.

Users and Administrator Accounts

Review Users → All Users.

• Remove unused accounts.
• Create individual accounts for each person.
• Avoid shared administrator credentials.
• Use strong unique passwords.
• Assign the lowest appropriate role.
• Confirm email addresses and display names.
• Enable multi-factor authentication through an appropriate solution.

Ensure the organization controls at least one administrator account and recovery method.

Themes and Plugins

Review installed software.

• Update everything.
• Remove unused plugins.
• Remove unused themes while retaining an appropriate fallback theme if required by your maintenance policy.
• Confirm plugin ownership, purpose and documentation.
• Avoid activating several overlapping tools without a plan.

Deactivated code can still contain vulnerabilities if files remain on the server. Remove software that is not needed.

Updates

Open Dashboard → Updates and review automatic update choices.

Establish a process for:

• WordPress core.
• Plugins.
• Themes.
• Translations.
• Compatibility testing.
• Backups and rollback.

Security updates should not be delayed without a strong reason and mitigation plan.

Site Health

Open Tools → Site Health.

Review critical issues, recommendations and information about the installation.

Site Health can expose details about:

• WordPress configuration.
• Server environment.
• Themes and plugins.
• HTTPS.
• Filesystem.
• Database.
• Scheduled events.
• Debug settings.

It is a diagnostic starting point, not a substitute for monitoring and professional review.

Email Delivery

Test whether WordPress can send essential email.

Examples include:

• Password reset.
• Administrator notifications.
• Form confirmations.
• Order email.
• Account registration.

Production websites often benefit from a dedicated transactional email service rather than relying only on basic server mail.

URL and HTTPS Checks

Confirm:

• The preferred www or non-www hostname.
• HTTP redirects to HTTPS.
• WordPress URLs use HTTPS.
• No mixed-content warnings appear.
• Canonical URLs are consistent.
• Administration and login use secure connections.

Remove Default Content

Delete or replace:

• Sample post.
• Sample page.
• Default comment.
• Unused widgets or patterns.
• Placeholder navigation.

Do not leave public demonstration content that suggests the website is unfinished.

Configure Backups and Monitoring

Before launch, confirm:

• Files and database are backed up.
• Backups are stored separately.
• Retention is sufficient.
• Restoration has been tested.
• Uptime monitoring is active.
• Error and security monitoring have owners.

Post-Installation Checklist

Before building or launching, verify:

• Site title and tagline.
• Correct URLs.
• Administration email.
• Language and time zone.
• Registration policy.
• Homepage and posts page.
• Search engine visibility.
• Comment policy.
• Media sizes.
• Permalink structure.
• Privacy page.
• User roles.
• Themes and plugins.
• Update workflow.
• Site Health.
• Email delivery.
• HTTPS redirects.
• Backups and monitoring.

Frequently Asked Questions

What is the most important setting to configure first?

Confirm the site URLs, environment, language, time zone and search visibility before publishing content. Permalink structure should also be decided early.

Should I use the post name permalink structure?

It is a common readable choice, but migrations, publications and specialized content may require another stable structure.

Is the search engine visibility checkbox enough for staging?

No. It requests that search engines avoid indexing but does not prevent access. Protect staging with authentication or network controls.

Should automatic updates be enabled?

The answer depends on the website’s risk, testing and maintenance process. Security fixes should be applied promptly, while complex sites may need controlled testing and deployment.

Continue Learning

Previous: The WordPress Dashboard and the Public Website

Next: WordPress Files and Database: A Beginner’s Overview