Insights, ideas and inspiration. A go to wisdom hub right here.
Featured Posts
Tutorials
7 Min Read
Latest Posts
Tutorials
11 min read
How to find broken links in Google Analytics 4 (GA4)
Introduction
Visitors expect a smooth experience on your website, but broken links and 404 errors can disrupt that, harming your brand, conversions, and SEO.
When users encounter dead links, they’re likely to leave your site, increasing bounce rates and reducing conversions.
In this guide, we'll walk you through the steps on how to find 404 errors and dead links in Google Analytics 4.
We find 404 links using these three methods
- Method 1: Using GA4 Engagement Reports
- Method 2: Using GA4 Custom Reports
- Method 3: Using GA4 custom events via Google Tag Manager
So let’s get started!
What is a broken link?
A broken link, commonly referred to as a 404 error, is a hyperlink that leads to a web page that no longer exists or cannot be found.
These pesky errors can occur for various reasons—maybe the page was moved or deleted, or the URL was entered incorrectly.
For example, if you try to access a page with the URL yourwebsite.com/blog/how-to-find-broken-links but the page no longer exists, you’ll encounter a 404 error.
Types of broken links
Hard Broken Links
A hard 404 error happens when a page doesn't exist, and the server correctly shows a "Page Not Found" message with a 404 error code. This tells users and search engines the page is gone.
Soft Broken Links
Soft 404 occurs when a non-existing page still loads, but instead of showing a proper 404 error, it might redirect to the homepage or a custom "Not Found" page without the right error code. This can confuse search engines and impact your site's SEO.
What Impact Do Broken Links Have on Your Website?
Broken links frustrate visitors, leading to poor user experience, reduced trust, and lost conversions. They negatively affect website SEO by signaling to search engines that your site isn’t well-maintained, which can lower rankings.
Additionally, broken links disrupt the flow of navigation, making it harder for visitors to engage with your content or complete desired actions. Fixing them is essential for maintaining a professional, functional, and search engine-friendly website.
How to set up Google Analytics 4 to track broken links
Method 1: Using GA4 Engagement Reports
In this method, we use the default reports tab under the main menu.
Step 1: Check the Page title of your website’s 404 Page
- First, find out the page title of your website’s 404 page.
- For this method, we use the Analytics account of Google Merchandise Store
- Enter the URL https://shop.merch.google/xyz and note down the 404 Page Title
Screenshot 1: Google Merchandise Store Page Unavailable
- The title of the page says Page Unavailable.
- Check the page title of your website’s 404 web page. Page not found is a common page title of 404 error pages.
Step 2: Setup and engagement report in Google Analytics 4
- Login to Google Analytics 4 GA4
- Navigate to Reports.
Screenshot 2: Click on reports
- Click on the Engagement dropdown and select Pages and Screens.
Screenshot 3: Select Pages and Screens
- After clicking on Pages and Screens the following report will appear, as shown in the screenshot below.
Screenshot 4: Pages and Screens Report
- Select the Page title and screen class.
Screenshot 5: Select Page Title and Screen Class
- Click on the search bar as shown in the screenshot below.
- Type the page title of the 404 page, which is “Page Unavailable,” and press enter.
Screenshot 6: Paste the Page Title of the 404 page
- At this step, we got aggregated data of 404 pages.
- Click on the “+” icon as shown in the screenshot below and add a secondary dimension to the Page path and screen class.
Screenshot 7: Click on the “+” Icon
- Select the Page path and screen class as shown in the screenshot below.
Screenshot 8: Select Page path and screen class
- Once it’s done, you will see the list of 404 pages with the URLs shown in the screenshot below.
Screenshot 9: Ga4 engagement report List of 404 Pages with URLs
Method 2: Using GA4 free form exploration technique
In this method, we use the free from exploration report tab under the explore menu.
Step 1: Create a free from exploration
- Logging in to your Google Analytics account
- To start a custom report, click on the Exploration tab on the left-hand side
- Click on the blank Exploration to start a new exploration.
Screenshot 10: Blank Exploration Report
Step 2: Add Dimensions
- Let’s add Dimensions by clicking on the “+” icon.
- On the search bar, type Page.
- Select the following Dimensions and add it to Rows
- Page path and screen class
- Page title
Screenshot 11: Select Dimensions
- Now drag and drop or select the Dimensions from the Variable Tab to Rows in the Settings Tab.
Screenshot 12: Drop the Dimensions In Rows
Step 3: Add Metrics
- We will now head over to the Metrics, and add the view metric
- As we added the Dimensions do the same for the Metrics by clicking the “+” icon and then clicking on Confirm.
Screenshot 13: Select Views Metrics
Screenshot 14: Drop the Views metrics in Values
Step 4: Filter Data
- Next, we will filter the report by using Filters.
- Select the Page Title in Filters. Select match type as contains.
- In Enter expression text box, type the error page title. GA4 will autocomplete the text, and you will get a drop-down list of pages.
- Select Page unavailable and click Apply.
Screenshot 15: Apply filters
- Below we will get the Final Custom Report of the Exploration.
Screenshot 16: 404 URLs in free form reports
Method 3: Using GA4 custom events via Google Tag Manager (GTM)
- This method uses the Google Tag Manager data layer to send a custom event to GTM.
- A few pre-requirements are that you must have installed GTM on your website and configured it. You can use Google Sitekit WordPress plugin to install GTM.
Step 1: Push a custom 404 event to the Google Tag manager
- First, let’s push a custom event to Google Tag Manager (GTM) to track 404 errors.
- To do that first, we have to add a custom script to the functions.php file in the WordPress theme. For this tutorial, we are using the WordPress Twenty Twenty-four theme.
- A few things to consider when adding custom code to your theme
- We recommend adding custom code to the child theme's functions.php file instead of the parent theme’s functions.php.
- To know more about creating a child theme, go through the Themes Handbook.
- Before making any changes to your site we recommend, that you should always back it up.
- At the minimum, you should make a copy of your child theme’s functions.php (if you have already created it and edited it) since we are modifying it. If something goes wrong when you are adding code to it, then you can restore it.
- Here is a script to add to your WordPress child theme‘s functions.php
- An add_404_custom_event callback function is added to the wp_head hook. The script below will be added to the HTML head tag.
<?php add_action( 'wp_enqueue_scripts', 'theme_enqueue_styles' ); function theme_enqueue_styles() { $parenthandle = 'twentytwentyfour-style'; $theme = wp_get_theme(); wp_enqueue_style( $parenthandle, get_template_directory_uri() . '/style.css' ); wp_enqueue_style( 'child-style', get_stylesheet_uri(), array( $parenthandle ) ); } add_action( 'wp_head', 'add_404_custom_event' ); // Code for sending custom event to data layer function add_404_custom_event() { // Ensure the script runs only on 404 pages if (is_404()) { ?> <script> wiindow.dataLayer = window.dataLayer || []; window.dataLayer.push({ 'event' : 'page_not_found_404' // Name it whatever you like }); </script> <?php } // is_404 check } |
- Inside the function, we first check if the page is a 404 page. If yes, we push a custom event page_not_found_404 to the data layer of GTM.
- Once you have added the above code in the functions.php file, save it and upload it to the child themes folder.
- Next, head over to your Google Tag Manager’s Overview tab.
- Click on the preview button on the toolbar, as shown in the following screenshot below.
Screenshot 17: Click on the Preview button
Screenshot 18: Tag Manager Preview Mode
- In the Your website's URL textbox, enter the 404 error URL; for example, add ssss to your base URL, for e.g. yourwebsite.com/ssss
- Uncheck the checkbox; include a debug signal in the URL.
- Click on Connect. This will open the entered URL in a new window, as shown in the below screenshot (number)
- Note : Ensure you are not logged in as a WordPress user since the Google Sitekit plugin excludes logged-in users from tracking in Google Analytics 4 and GTM. Hence the custom event will not be fired and will not be available in Datalayer.
Screenshot 19: Tag assistant connected page in New Window
Screenshot 20: Tag manager connected Dialog box
- Once Tag assistant is connected, click on the Continue button
- On the summary pane of the tag assistant screen, you will see the custom event fired.
Screenshot 21: page_not_found_404 event
Step 2: Send the 404 custom event to GA4 using the trigger
- Go to the Trigger menu in the Google Tag Manager
- Click on the New Button to create a trigger
Screenshot 22: GTM Workspace Triggers
Screenshot 23: Name the Trigger
- First, name the Trigger something descriptive. For example, Trigger (Page Not Found 404)
- Next, click anywhere on the Trigger Configuration section to enable edit mode.
- A Choose trigger type overlay panel will open up. Scroll down to the Other event group and select Trigger Type as Custom Event.
Screenshot 24: Set Trigger Type as a custom event
Screenshot 25: Trigger event as page_not_found_404
- Enter the event name that you have added in the data layer (page_not_found_404).
- Keep the radio selection of trigger fires on to All custom Events.
- Click on the Save button.
- Note: This step is crucial; make sure the event name you enter here exactly matches the event name that you pushed using the data layer push function.
Step 3: Setup a GA4 Event tag to send the custom event to Google Analytics 4
- Head over to the tags sub-menu in the Tag Manager
- Click on the new button to create a new tag
Screenshot 26: Create a new Ga4 event Tag
- Name the tag to something relevant. For e.g GA4 tag (page_not_found_404 event)
- Next, click anywhere on the Tag Configuration section to enable edit mode.
Screenshot 27: Click on the Trigger Configuration section to enable edit mode.
Screenshot 28: Choose tag type Google Analytics
Screenshot 29: Select Google Analytics: GA4 Event tag
- Enter the measurement ID of the Google Analytics Web stream to which you want to send the custom event.
- Enter the event name, as page_not_found_404
Screenshot 30: Enter the measurement Id of the GA4 web stream
- Choose the trigger that we created in Step 2. To do that, click anywhere on the Trigger section to enable edit mode.
Screenshot 31: Choose a trigger
- Once the trigger is added, click on the Save button.
Screenshot 32: Page not Found trigger
Step 4: Test the custom GA4 event tag in the debug view
- Go to the Admin menu.
Screenshot 33: Admin menu of Google Analytics 4
- Next, head over to Data Display > DebugView. You will see the newly custom event page_not_found_404.
Screenshot 34: page_not_found_404’ event DebugView
- If everything works fine, publish your changes in Google Tag Manager by clicking the Submit button in the top right corner.
Screenshot 35: Submit workspace changes
- A Submit Changes overlay panel will show up.
- Enter the version name for e.g. Workspace version (Page not found) along with the description.
- Click on the Publish button.
Screenshot 36: Save Submission configuration
- When the changes are submitted, you will see a Version Summary slide over panel, as seen in the screenshot below.
Screenshot 37: Version Summary of Published Workspace changes
- That’s it. You have now added a custom event for 404 and sent it to the Google tag manager. Whenever a 404 page is hit, it will send a custom event, and we will use it to create reports for 404 links.
Step 5: Create a free form report in GA4 to view 404 pages
Screenshot 38: Explore menu in Google Analytics 4
- Click on Explore menu in Google Analytics 4.
- Choose Free Form Exploration.
Screenshot 38: Free form Exploration
- Name the exploration for e.g. Page Not Found 404 Report
- Add the Dimension to the Rows
- Page path and screen class
- Event Name
- Add Metrics to the Values
- Event Count
- Add filter
- Dimension: Event Name
- Condition: exactly matches
- Expression: page_not_found_404
Screenshot 39: GA4 GTM 404 variables and settings URLs
Screenshot 40: Page not found 404 links report
- That’s it we can see page not found URLs in the Free Form report.
Conclusion
In Method 1 and Method 2, we found 404 errors using the Page title of the 404 error page, and in Method 3, we pushed a custom event to the Data layer of Google Tag Manager, which is then sent to GA4 using triggers whenever a 404 error page is found.
By regularly monitoring for broken links, you ensure that every visitor enjoys a frustration-free experience. An error-free website isn’t just good for your users—it’s great for your business.
Tutorials
9 min read
How to integrate a Helpdesk and Customer Support Ticket System in WordPress using SupportCandy (Part 3)
Introduction
In Part 2 of this 3 part Blog series, we covered the following sections of the support candy plugin
- Ticket List
- Agent Ticket List
- Customer Ticket List
- Email notification
Now, in Part 3 which is the final part of this blog, we will explore the settings sections of the SupportCandy plugin.
Settings
Step 1: General settings
- Under this tab, you can configure the general settings.
Screenshot 1: Settings → General Tab
- Ticket Status After Customer Reply: You can define the ticket status that will be set when a customer (the ticket creator) submits a reply. If you don't want the status to change, select the "Do not change" option.
- Ticket Status After Agent Reply: You can specify the ticket status that will be applied when an agent submits a reply. To keep the status unchanged, select "Do not change."
- Close Ticket Status: This status is applied when either an agent or a customer closes the ticket.
- Ticket Alice: You can customize the name used for your tickets. For example, you might rename it to "Case," so tickets will be referred to as "Case #" in individual tickets, email notifications, and other communications.
- Allow Close Ticket: You can determine who has permission to close a ticket. Agents from the selected roles must have the necessary access to enable the "Close" button within an individual ticket.
Page settings Tab
- Here you can set the various pages such as user login and registration screens.
Screenshot 2: Support → Settings → General Settings → Page Settings tab
- Support Page: The support page is where the [supportcandy] shortcode is used on the front end to display the support functionality.
- User Login: This setting determines how users can log in to access the support forum on the front end. You can choose from Default, WP Default, or Custom URL options.
File Attachments
- Go to Support → Settings → General Settings → File Attachments tab
- Here you can set the max file size of the attachment along with its Allowed File Extensions.
Screenshot 3: File Attachments tab
Thank you page
- Here you can define what action should be taken after the customer or agent submits the ticket.
Screenshot 4: Thank You Page
- You can show a thank-you text, redirect to the custom page, or open a ticket page.
Step 2: Dashboard
- Dashboard in SupportCandy lets support agents quickly see important ticket information. This helps them plan their work and choose what to do first.
- You can see how many new tickets, unresolved tickets, unassigned tickets, closed tickets, tickets assigned to the current agent (mine), tickets that are out of SLA, tickets that are due today, and tickets that are due tomorrow.
- If an agent clicks any of these numbers they will be redirected to the respective categories list of tickets with the right filter in place.
General
- Here we define the general settings for the dashboard, such as the default date range and dashboard auto-refresh.
Screenshot 5: Dashboard General Tab
Cards
- Under this tab, set the order of the tickets based on the ticket status.
Screenshot 6: Dashboard Cards
- Click the Edit button next to that card, as shown in the screenshot below . You can change the Title, show/hide the card in the dashboard, and allow agent roles who can see the card info in the dashboard.
Screenshot 7: Edit the Cards
Widgets
- The dashboard widgets give you a complete view of your support operations, with real-time information on new tickets and closed tickets, as well as full analytics on response times and communication gaps.
- You can customize the dashboard to your needs by rearranging widgets based on priority.
- Also, you can manage visibility for different agent roles by enabling or disabling widgets for specific roles.
Screenshot 8: Dashboard Widgets
Here is the List of widgets that are available by default
- Ticket Statistics
- Trends of Today
- Agent Workload
- Recent Activity
- Recent Tickets
- Unresolved Tickets by Type
- Unresolved Tickets by Priority
- List of Unresolved Tickets by Status
- Response Delay
- Ticket Closing Delay
- Communication Gap
- Ticket comments
- Agent scores
- Out of SLA Tickets
- Active Timer
- Usergroups
Adding a new widget
- In the Widgets tab, locate the Add New Widget button and click on it.
- Select the Custom field for which you want to add widgets. Click Submit to save changes.
Screenshot 9: Adding a new widget
Editing the Widgets
- Click on the edit icon beside the widget name.
- You can change the title, show/hide the widget in the dashboard, and allow agent roles who see the widget in the dashboard.
Screenshot 10: Editing Widgets
Step 3: Ticket Categories
- Ticket categories let users and agents sort tickets into groups based on what they are about, which makes it easier to communicate and solve problems.
Screenshot 11: Ticket categories
Adding a New Category
- Users with the necessary permissions can create new ticket categories.
- Navigate to Support → Settings → Ticket Categories
- Click on Add New.
- Give a name to the category.
- Select the order of loading the categories by Load after dropdown.
- Click Submit
Screenshot 12: Add New Ticket Category
Edit Category
- Click on the Edit option beside the name of the ticket.
- You can change the name and loaf after settings.
- Click Submit.
Screenshot 13: Edit Ticket Categories
Step 4: Ticket Statuses
- Under this tab you can set your own custom statuses to customize the process and life cycle of the tickets.
- Customization includes the color patterns that go with each status, which show clearly what state the ticket is in.
- Administrators can edit or delete statuses as needed.
Screenshot 14: Ticket Status
Adding Status:
- Head over to Support → Settings → Ticket Statuses.
- Click on Add New.
- Enter a suitable name for the new status that you want to add.
- Choose a color and background color for visual identification.
- Click Submit.
Screenshot 15: Adding status
Edit Status:
- Click the Edit link beside the status name that you want to edit.
- Edit the color, background color, and load after setting.
- Click Submit.
Screenshot 16: Editing a Ticket status
Step 5: Ticket Priorities
- Using this setting, you can prioritize tickets based on urgency. You can create new priorities or edit existing ones (High, Medium, Low priorities).
Screenshot 17: Ticket Priorities
Adding a New Priority
- Go to Support → Settings → Ticket Priorities and click on Add New.
- Enter a name and choose a color and background color for the priority based on its urgency.
- Click Submit.
Screenshot 18: Adding a new Ticket Priority
Edit Priority
- Click on the edit link for which you want to edit.
- Click on the Edit option.
- Edit the Name, Color, or Background color, Load after settings as per your needs.
- Click Submit
Screenshot 19: Editing Ticket Priorities
Step 6: Miscellaneous
- Under the Miscellaneous settings, you can set the following settings:
- Term & Conditions
- GDPR
- reCaptcha
- Advanced
Terms and conditions
- Enabling this feature will add a checkbox in the Create Ticket form and Registration Form prompting the user to agree to the terms and conditions.
- The terms and conditions message can be customized as seen in the below screenshot no.. You can also add to link to your terms and conditions page.
Screenshot 20: Miscellaneous → Terms & Conditions
GDPR
- If enabled, it will add a checkbox in the Create Ticket form and Registration Form with a custom message letting the user know what information will be stored in the database.
- You can also send the Personal data retention
- It specifies the duration for which the system should retain personal information within the ticket. Once the retention period has passed, the database will either delete or anonymize personal details such as Name, Email Address, IP Address, and any custom fields marked as personal information, from the date of creation.
- If you wish to retain personal information indefinitely, set the retention period to 0 days.
Screenshot 21: Miscellaneous → GDPR
reCaptcha
- You can add Google reCaptcha to the ticket form, login and registration screen, profile screen, etc.
- For that, you need to generate the Site key and Secret key from this link.
Screenshot 22: Miscellaneous → reCaptcha
Advanced Settings
- Here you can configure 25 types of advanced settings. We will discuss the main settings for now.
- Reply confirmation: After clicking the reply button on a specific ticket, the system will prompt the user for confirmation.
- Ticket ID: In this setting, you can choose whether new ticket IDs are assigned sequentially or randomly.
- Starting Ticket ID: Within the Sequential Ticket IDs setting, you can specify the initial ticket ID to be used for new tickets.
Screenshot 23: Miscellaneous → Advanced settings
Step 7: Ticket Widgets
- The Ticket widgets are displayed on the single ticket in the backend. You can manage the access levels for each widget, determining who can view or edit them.
- Also, you can rename, enable, or disable, and change the order of the widgets from this settings tab.
Screenshot 24: Support → Settings → Ticket Widgets
Screenshot 25: Edit Ticket Widgets
Step 8: Rich Text Editor
- This setting allows you to manage the rich text editor configurations for Agents, Registered Users, and Guest Users.
Screenshot 26: Rich Text Editor Agent Tab
Screenshot 27: Rich Text Editor Registered User Tab
Screenshot 28: Rich Text Editor Guest user Tab
- Enable: You can enable or disable the rich text editor for users.
- Allow Attachments: You have the option to allow or disallow attachments in various areas such as ticket descriptions, reply descriptions, and note descriptions.
- Toolbar Actions: The rich text editor allows you to select which actions to enable, including:
- Bold
- Block quote
- Italic
- Align
- Right to left
- Underline
- Bulleted list
- Link
- Text background color
- Image
- Numbered list
- Strikethrough
- Show File Attachment Notice: You can choose to display information about file attachments, including allowed file types and sizes, to users. This can be configured in the user types setting.
- HTML Pasting: When activated, any text that is copied to the clipboard will be pasted with HTML.
Screenshot 29: Rich Text Editor Advanced Tab
Step 9: Working Hours
- This section allows you to choose the working hours for your company or organization. These specified hours will act as a standard template for the working hours of agents.
Screenshot 30: Support → Settings → Working Hours
Holidays
- In this setting, you can add holidays for your company or organization,
- You can add a single holiday by clicking on a single date or multiple holidays by date range (selecting and dragging),
- After electing choose the action Add new holidays.
- If you want this to occur annually select yes in Repeat every year drop-down.
- Similarly, you can delete holidays.
Screenshot 31: Holidays Calendar
Screenshot 32: Add/Delete Holidays
Exceptions
- In some situations, you may want to modify the working hours for a specific day. You can do this by selecting that specific date and modifying the working hours.
- This exception will apply only to the working hours set at the company or organization level.
Screenshot 33: Working hours → Exceptions list
Screenshot 34: Working hours → Exceptions → Add New
Settings
- In the Settings Tab, you can Allow agents to modify working hours or you can Allow agents to modify their leaves.
Screenshot 35: Working hours → Settings Tab
Step 10: Appearance
- You can configure the appearance of General (overall look and feel), Ticket List, Individual Ticket, Modal Popup, Agent Collision, and Dashboard screens.
Screenshot 36: Appearance
Step 11: Ticket Tags
- The Ticket Tag Setting feature allows administrators to add tags to the tickets.
- To add a ticket tag enter its name and description, and select its color and background color.
Screenshot 37: Add new Ticket tag
- Under the same screen, you can customize Tag Appearance for ticket tags.
Screenshot 38: Ticket Tags General (Customizing Tag Appearance)
Conclusion
In this blog, we walked you through how to add a helpdesk and ticket system on WordPress using the SupportCandy plugin.
SupportCandy adds to your WordPress site the features of a complete help desk and customer support ticket system. It is one of WordPress's most popular helpdesk and customer support ticketing plugins.
That’s it for this article. Do more with your website.
If you need any help related to WordPress, contact our WordPress experts.
Tutorials
9 min read
How to integrate a Helpdesk and Customer Support Ticket System in WordPress using SupportCandy (Part 2)
Introduction
In Part 1 of this 3 part Blog series, we covered the basics of setting up the Support Candy plugin, focusing on the following sections of the plugin
- Installation and Setting up the Plugin
- Tickets
- Customers
- Support Agents
- Custom fields
Now, in Part 2 of this Blog, we will explore the following sections of the SupportCandy.
- Ticket List
- Agent Ticket List
- Customer Ticket List
- Email notification
Ticket List
- Ticket List section is used to define the columns that appear in the Admin and Agent dashboard under Tickets → Ticket List screen and Customer Tickets list on the front end.
- You can add new columns from the existing list of items or rearrange the columns order in which they are displayed.
Step 1: Agent Ticket List
List Items tab
- Go to the SupportCandy plugin menu.
- Click on the Ticket List → Agent ticket list → List items
- Customize the column order displayed in the ticket list.
Screenshot 1: Item Lists
Adding List Items (Coulmns) to Tickelt list table
- Click on Add new to Add new List items.
- Select fields from the available list (e.g. date created, email address, etc) as shown in the below screenshot.
- Hit Submit to save changes.
Screenshot 2: Adding New Column to Agent Ticket List table
Editing List Items
- In the Agent Ticket List section, edit the column that you want to reorder.
- Click Submit to apply your changes.
Screenshot 3: Edit List Items (reordering columns)
Filter Items
- This screen allows us to add filter options for filtering tickets on the Agent Tickets list screen. You filter tickets based on their status, customer, subject, category, priority, and so on.
Screenshot 4: List of available filters in the Agent Ticket List
Add New Agent Tickets Filter Items
- Go to the Ticket List → Agent ticket list → Filter items.
- Add the filter options you want to filter tickets by, as shown in the screenshot below.
- Click Submit to apply the filter settings.
Screenshot 5: Add New filter options to Agents Tickets
Edit Agent tickets Filter Items
- Go to the Ticket List → Agent ticket list → Filter items. Click the Edit link beside the field.
- You can only change the Load after setting
- Click Submit to apply your changes.
Screenshot 6: Edit filter item for Agents Tickets
Default Filters
- Default filters are filters on the ticket list. Here we choose the fields created in the above steps. These filters are available to agents.
- Select the items for default filters drop down on the Ticket List page (e.g., All, Unresolved, Unassigned, Mine, Closed, Deleted, show only open tickets).
- Drag and drop to reorder the fields as needed.
Screenshot 7: Agent Ticket List Default filters
Add new Agent ticket list Default Filters
- Go to Ticket List → Agent ticket list → Default filters
- Enter the Label, choose the Parent filter if needed
- If required apply conditional logic.
- Set the Enable drop-down to Yes
- Click Submit.
Screenshot 8: Add new Default filter
Edit Agent tickets Default Filter
- Go to Ticket List > Agent ticket list > Default filters
- Click on the edit icon beside the filter name
- You can only edit the Label and its Enable status.
Screenshot 9: Edit Default filters
Step 2: Customer Ticket List
- Similar to Agent ticket list we can define columns for the Customer ticket list and add new filters to it.
Screenshot 10: Columns displayed in the Customer ticket list
List Items
- Go to the SupportCandy plugin menu.
- Click on the Ticket List → Customer ticket list → List items
- Customize the column order displayed in the ticket list.
Adding List Items (Coulmns to Tickelt List Table)
- Click on Add new
- Select fields from the available dropdown (eg. Name, email address, priority, etc.) as shown in the below screenshot.
- Hit Submit to save changes.
Screenshot 11: Custom ticket list → Add new list item
Editing List Items
- In the Customer Ticket List section, edit the column that you want to reorder.
- Click Submit to apply your changes.
Screenshot 12: Customer ticket list → Edit list item
Filter Items
- This screen allows us to add filter options for filtering tickets on the Agent Tickets list screen. You filter tickets based on it’s status, customer, subject, category, priority, and so on.
Screenshot 13: Filter fields for Customer tickets (frontend)
Add New Customer Tickets Filter Items
- Go to the Ticket List → Customer ticket list → Filter items.
- Add the filter options you want to filter tickets by, as shown in the screenshot below.
- Click Submit to apply the filter settings.
Screenshot 14: Add New filter options to Customer Tickets
Edit Agent tickets Filter Items
- Go to the Ticket List → Customer ticket list → Filter items. Click the Edit link beside the field.
- You can only change the Load after setting
- Click Submit to apply your changes.
Screenshot 15: Edit filter options to Customer Tickets
Default Filters
- Go to Support → Ticket List → Agent ticket list → Default filters
- You can set the default filters that appear in the customer tickets screen, similar to the Agent Agent tickets screen.
Screenshot 16: Default filters in the Customer Tickets list
Adding Default Filters to Customer Tickets
- Go to Support → Ticket List → Agent Customer list → Default filters
- Enter the label; choose the Parent filter if needed.
- If required, apply conditional logic.
- Set the Enable drop-down to Yes.
- Click Submit.
Screenshot 17: Adding Default Filters to Customer Tickets
Edit Customer tickets Default Filter
- Go to Ticket List → Customer ticket list → Default filters
- Click on the edit icon beside the filter name.
- You can only edit the Label and its Enable status.
Screenshot 18: Edit Customer tickets Default Filter
Step 3: More Settings
- Using the More settings tab, you can customize how the ticket list behaves for both agent and customer views.
- Here are the available settings for both:
- Default Sort By: Choose the default field by which tickets will be sorted.
- Default Sort Order: Set the default sort order (ascending or descending).
- Number of Tickets: Specify how many tickets will be displayed per page.
- Unresolved Statuses: Define the statuses that are considered unresolved.
- Default Filter: Set the default filter for the ticket list. Agents can adjust this further in their profile settings within the ticket portal.
- Ticket Reply Redirect: Choose what happens after a reply is added to a ticket. "No redirect" keeps the customer on the current ticket screen, while "Ticket list" redirects them back to the ticket list screen.
Agent view
Screenshot 19: More Settings Agent View
Customer view
Screenshot 20: More Settings Customer View
Advanced Tab
- You can define a closed ticket status group, where tickets with statuses in this group are treated as closed.
- Additionally, you can configure the default auto-refresh behavior for the ticket list. If enabled, the ticket list will automatically refresh every 10 seconds by default until you turn off this feature from the ticket list settings.
Screenshot 21: Advanced Tab
Email Notifications
- Using this menu, you can set up email notifications.
Step 4: General Settings
- Go to the Email Notifications section under the Support menu.
Screenshot 22: Email Notification → General settings
- Here, you can configure the following email settings:
- From name – Sender's name.
- From email – From which email address will the email be sent
- Reply To – When a user replies to a notification, emails will be sent to the specified email address. If no address is provided, the "From" email address will be used as the reply-to address.
- Number of emails per cron job – Set the maximum number of emails that should be sent in a batch.
- Blocked Emails – Specify email addresses that should not receive email notifications.
- Attachments in notifications – configure to send emails with attachments (links or actual files )
Step 5: Ticket Notifications
- In this section, you can edit or create email notification templates.
Screenshot 23: Ticket Notifications
Adding New Ticket Notification
Screenshot 24: Add New Ticket Notification
- Click on Add New.
- Add Title and Select a Trigger
- Following are trigger events that can be used to send email notifications
- Cricket new ticket: When a new ticket is created
- Ticket reply: When a ticket receives a new reply, relevant parties are notified to the new response.
- Change ticket status: When the ticket status changes, for example, from Open to Awaiting customer reply, the activation occurs.
- Change ticket category: When the category of the ticket is modified
- Change ticket priority: When the priority of a ticket is changed
- Change assignee: When the assigned agent of the ticket is changed, it will trigger a notification to the new assignee.
- Delete ticket: When a ticket is deleted,
- Submit private note: When a private note is added to a ticket
- You must change the notification status to Enabled. Otherwise, this email notification won’t be sent.
- You can use macros or placeholders within the Subject and Body.
Editing Ticket Notifications
- Click on Edit button beside the template name for which you want to edit.
- You can manually add recipients in To address (required), CC, and BCC using the following settings
- General Recipients
- Agent Roles
- Custom Email Addresses (one per line)
Screenshot 25: Editing Ticket Notifications
- You can Insert Macro in the email body
- Click on the Insert Macro button to view a list of available macros.
- The list will include placeholders for various types of data, such as customer name, status, date created, etc.
- Select the macro you wish to insert. For example, {{customer_name}} can be used to insert the customer's name dynamically.
Screenshot 26: Insert macro current user name
- After clicking on the Insert button, the user name macro has been added under the body, as shown in the below screenshot.
Screenshot 27: User name Macro
Conditions
- You can add And/Or conditions, and when they are met, then only an email notification is sent
- Let’s say that you want to send a notification for ticket change status to the Awating agent reply.
- Click on Add New under the Email Notifications → Ticket Notifications section. Set the trigger to Change Ticket status
- Under the Conditions section, set the Status equal Awaiting Agent reply.
- Add the subject, body, and email addresses to which this notification should be sent.
- Click Submit. Just now you configured that this notification should be sent when the status is Awating agent reply.
Sccreenshot 28: Setting Conditions in Ticket Notifications
Step 6: User Registration OTP
- This screen is to configure the email template for the Default registration of the supportcandy plugin. You can customize the email template that is used to send the OTP.
- The user registration OTP is a single-use password that is sent to verify the user's email address when using the “Default” registration form.
- Within the body section of the setting, you can utilize macros (placeholders) in the email subject and body as shown below.
Screenshot 29: User Registration OTP
Step 7: Guest Login OTP
- To allow guest users to access their ticket list, you can activate an OTP (One Time Password) login.
- Keep in mind that OTP login is functional only when guest tickets are enabled. You can turn on this feature by navigating to Support → Settings → General Settings → Page Settings.
- Under the Guest Login OTP setting, you have the option to change the email template used for sending the OTP.
- On the same setting page, you can insert macros (placeholders) into the email subject and body.
Screenshot 30: Guest Login email notification template for OTP
Conclusion
In this blog (Part 2 of the 3 Part Blog series), we walked you through the Ticket List, Customer Ticket List, Agent Ticket List and Email Notifications Sections.
That’s it for this article.
In the upcoming Part 3 of this series, we'll explore even more advanced features to take your customer support to the next level.
If you need any help related to WordPress, contact our WordPress experts.
Tutorials
12 min read
How to integrate a Helpdesk and Customer Support Ticket System in WordPress using SupportCandy (Part 1)
Introduction
In today's competitive landscape, providing exceptional customer support is a top priority for businesses to maintain a loyal client base. Whether you run an online eCommerce store, a membership site, a product, or a service-based business, having a robust customer support system is essential for maintaining a positive customer experience.
Integrating a helpdesk and customer support ticket system directly into your WordPress website can be a game-changer.
In this step-by-step guide, we'll delve into the process of integrating a robust customer support ticket system into your WordPress website using the SupportCandy plugin.
This is a three-part blog series. In this Part 1 article, we discuss the following sections of the SupportCandy.
- Installation and Setting up the Plugin
- Tickets
- Customers
- Support Agents
- Custom Fields
The step-by-step process of adding a customer support system to WordPress using the SupportCandy
Step 1: Installing the SupportCandy plugin
- In the beginning, go to your WordPress homepage.
- For the Plugins tab, click on it.
- Press the Add New button.
- Use the search bar to look for SupportCandy.
Screenshot 1: Click on Add New Plugin
- Click the Install Now button under the plugin SupportCandy—Helpdesk & Support Ticket System.
- Click the Activate button, and you are done!
Screenshot 2: Install and Activate the Plugin
Step 2: Setting up Frontend Pages
Once the plugin is activated, we need to create web pages to embed SupportCandy shortcodes to display various support-related features and functionality.
Support requests Page
- Go to the WordPress Pages menu. Click on the Add New Page. Name the page Supports Requests.
- Add the shortcode ‘[supportcandy]’ to this page and save it.
- Go to the Support Candy menu Support → Settings → General Settings → Page Settings.
- Select the newly created page Support Requests under the Support page dropdown.
- Save the settings by clicking the Submit button.
Screenshot 3: Create a New WordPress Page Support Requests
Screenshot 4: Add it to Support → Settings → General Settings → Page Settings
Tickets
Step 3: Ticket List (Viewing Tickets)
- Navigate to the Tickets section under the SupportCandy menu.
- Here you will see a list of all tickets.
- Use the filters and search bar to find specific tickets.
Screenshot 5: Ticket List
- Click on an individual ticket to view the ticket details, such as ticket status, ticket info, and comments, as shown in the below screenshot 6.
Screenshot 6: View single ticket details
Step 4: Viewing Dashboard
Screenshot 7: Dashboard
- At the top of the dashboard, we can see numbers of New, Unresolved, Unassigned, and Closed Tickets.
- Below that we can see various cards, such as
- Ticket Statistics
- Today's Trends
- Agent Workload
- Recent Activities
- Recent Tickets
- Unresolved tickets by Category, Priority, and Status (default: last 7 days data)
- Ticket statistics by day of the week
- You can choose which cards to display in this dashboard under the settings menu, which is discussed in the default tab under Agent Profile.
Step 5: Adding a New Ticket
Adding a New Ticket from Frontend
- Your customers can add a ticket from the front end.
- Go to the Support Requests page that we created in Step 2.
- Click on the hamburger menu on the right side of the ticket list.
Screenshot 8: Slideover
- Click on New ticket.
- Add a subject or short description of the ticket.
- Add a detailed description of the ticket.
- Select the category.
- Agree to all terms and conditions.
- Click on Submit.
Screenshot 9: Adding a New Ticket from the Frontend
Adding a New Ticket from the backend
- In some situations, Support agents need to create tickets. Agents can add tickets from their accounts using this screen.
- Click on Support → Tickets.
- Click the New Ticket tab.
- In the Customer section, select the customer for whom you wish to create a ticket.
- Add a subject or short description of the ticket.
- Add a detailed description of the ticket.
- Select the category.
- Agree to the terms and conditions and click submit to save details.
Screenshot 10: Adding a New Ticket from the Backend
Step 6: My Profile
- Since we have already logged in as administrators, we can view our profile.
- If you want to update your name, you can do it on the My Profile screen.
- Hit Save Changes to save your name.
Screenshot 11: My Profile
Step 7: Agent Profile
Screenshot 12: Agent Profile
- You can set the signature used for emails using the screen.
- Default filters on the Ticket List tab can be set from here. You can choose from Unresolved, Unassigned, Mine, Closed, and Deleted tickets.
- The default tab for the Support main menu can be set from here. You can choose from the available options Ticket List, Dashboard, and New Ticket.
Customers
Step 8: Managing Customers
- Go to the SupportCandy plugin menu.
- Click on the Customers, submenu.
- Here you will see a list of all registered customers.
- You can select between All Users or Users who have tickets to filter the customer list.
Screenshot 13: Filter Customers
Screenshot 14: Edit Customer Info
- You can edit the customer information by clicking the edit button or view it by clicking the view button.
- When you click on the customer name, it will take you to his ticket list, as shown in the screenshot 15. There are 3 subtabs. Tickets, Custom Fields, Other.
Screenshot 15: Customers → Tickets
- The Tickets tab shows all the tickets of a particular customer.
- Other tabs shows Recent Activities related to that customer.
Screenshot 16: Customers Recent Activities
Support Agents
Step 9: Managing Agents
Adding a New Agent
- First, there should be a WordPress user account for the person to whom you wish to add an agent.
- Go to the SupportCandy plugin menu.
- Click on Support Agents.
- You can see all the agent lists in the screenshot 17.
- Click on Add New Agent.
- Search for the name from the list of WordPress users, for which you want to add as an agent.
- Select Role (Administrator, Agent, Editor, etc.)
- Click Submit.
Screenshot 17: Agent List
Screenshot 18: Adding a new Agent
- You can also edit the agent role from the edit link or delete an agent using the delete link.
- The Edit link allows update roles (Administrator, Agent, Editor, or any custom role that you have added).
Step 10: Agent Roles
You can create an agent role and set its capabilities on this screen. By default, there are two roles, as follows:
- Administrator: Has all possible capabilities.
- Agent has limited capabilities.
Screenshot 19: Agent Roles List
Adding a New Role
Screenshot 20: Assign agent capabilities
- Click on Add New Role.
- Specify the role name (label).
- You can grant permission for the following tickets:
- Unassigned: Tickets that have not been assigned to any agent or agent group.
- Assigned to me: Tickets that are specifically assigned to the current agent.
- Assigned to others: Tickets that are assigned to agents other than the current agent, but are not unassigned
- A few of the capabilities (actions that agents can perform)
- View Tickets: Controls read permission for applicable tickets. Agents who create tickets have read permission by default.
- Reply Tickets: Controls reply permission for applicable tickets. Agents who create tickets can reply by default.
- Private Notes: Controls permission to submit or read private notes on applicable tickets.
- Assign Agents: Controls permission to assign agents to applicable tickets.
- Change Status: Controls permission to change the status, category, and priority of applicable tickets.
- Change Ticket Fields: Controls permission to update ticket fields for applicable tickets.
- Change Agent-only Fields: Controls permission to update agent-only fields for applicable tickets.
- Change Raised By: Controls permission to update the ticket owner/creator for applicable tickets.
- Modify Additional Recipients: Controls permission to update additional recipients of applicable tickets. Ticket creators always have this capability.
- Edit Thread: Controls permission to edit/update threads of applicable tickets.
- Delete Thread: Controls permission to delete threads of applicable tickets.
- View Logs: Controls permission to view logs of applicable tickets.
- Delete Ticket: Controls permission to delete or restore applicable tickets.
- Here are additional permissions beyond ticket management:
- WP Dashboard Access: Grants an agent access to the WordPress dashboard. Without this, the agent can only view tickets from the front end, not the dashboard.
- Create Ticket on Others' Behalf: Allows an agent to create tickets on behalf of others.
- Deleted Filter Access: Allows agents to access the Deleted filter on the ticket list, enabling them to view deleted tickets. Without this, deleted tickets cannot be accessed.
- Edit Customer Info: Permits an agent to update customer information within individual tickets.
- Click Submit to save the new role.
Editing an Agent Role
Screenshot 21: Edit Agent Roles
- Under the Support Agents tab, click on Agent Roles.
- Select a role and click Edit.
- Make the necessary changes.
- Click Save.
- You cannot delete Administrator and Agent roles as these are the default roles.
Screenshot 22: Edit roles and permissions
Step 11: Working Hours
Configuring Working Hours
- Go to the Support Agents → Working Hours tab.
- Select the agent from the dropdown and then set the working hours.
- Click Submit.
Screenshot 23: Working hours
Working Hours Exceptions
- Exceptions allow for adjustments to standard working hours on specific dates. For example, if your typical working hours on a Monday are from 9:00 a.m. to 6:00 p.m. but you need to work from 9:00 a.m. to 2:00 p.m. on a particular Monday, you can set an exception to reflect this change.
- The system will then prioritize these modified hours over the usual schedule.
Screenshot 24: Exceptions
- Click on Exceptions.
- Add Title, Date, and Schedule
- Click Submit.
Step 12: Leaves
- You can set leaves or day-offs for the agents.
Screenshot 25: Leaves Calendar
- Click on the date for which you want to add leaves. Search for the agent name for which you want to grant leave and click submit.
Screenshot 26: Add leaves
Custom Fields
Step 13: Ticket Form Fields
- The Ticket Form Fields are the fields that are displayed on ticket form. This section lets you add or remove fields from the submit ticket form.
- If you want to add new fields to this form, Go to Support → Custom Fields → Ticket Fields, which is discussed next.
Screenshot 27: Ticket Form fields list
Add a field to the Ticket form fields
- Using Ticket Fields, Customer Fields, and Agent Only Fields you can add new fields to a ticket submission form.
- Ticket Fields: These are fields to collect more information from the customer (ticket subject, ticket description).
- Customer Fields: Fields to collect information about the customer. Name and email are default.
- Agent Only Fields: You can add fields specific to an agent.
Screenshot 28: Add a new field to the Ticket form
- The Add New Field screen has the following settings to be configured
- Select field: You can choose which fields from the ticket fields and user fields you want to add.
- Is required: Deciding whether the selected field is essential is up to you. If a field is marked as mandatory, it must be completed before submitting the report.
- Width: Within the form, it's possible to adjust the width of the area. There are three choices available: one-third of the row, half the width of the row, and the entire width of the row.
- Load after: This choice lets you change the order of the fields.
- Visibility conditions: The selected field can be displayed only when a specific situation is met. The fields will remain hidden as long as the conditions are not met. Conditions can be set using both AND logic (where all conditions must be met) and OR logic (where at least one condition must be met).
Editing Ticket Form Fields
- Go to the Support menu.
- Click Custom Fields → Ticket Form Fields.
- Click the Edit button next to a field you want to change to make changes.
- Click Submit.
- The name and email address fields are default; hence, you can only change the Width and Load after settings. Also, you can't delete them.
- For the rest of the fields, you can edit and delete them.
Screenshot 29: Editing the Subject Field
Step 14: Ticket Fields
- From the Ticket fields screen, you can create new fields to collect more information about tickets which can then be added to the New Ticket form.
Screenshot 30: Ticket fields
Adding New Ticket Fields
- Click Add New to create a new ticket field.
- Enter the label.
- Choose where will be this field loaded after.
- Choose the field type (e.g., text, dropdown, checkbox). Based on the field type, it will show more configuration options, such as Extra Info, Default Value, Auto-fill in ticket form, Character limit, Placeholder, Has personal info etc.
- Click Submit.
Screenshot 31: Adding New Ticket fields in the custom field
Editing Existing Ticket Fields
- Click Edit to edit a ticket field.
- Edit the field details such as Label, Subject, Load after, Extra info, Short description of the ticket, Default value, Not Applicable, Auto-fill in ticket form, Character limit, Placeholder, Ticket list width (pixels), etc.
- Once done Click Submit.
Screenshot 32: Editing Ticket fields in Custom fields
Step 15: Customer Fields
Screenshot 33: Customer Fields list
Adding New Customer Fields
- Click on the Add New button to create a new customer field.
- Choose the field type (e.g., text, dropdown, checkbox). Based on the field type, it will show more configuration options, such as Extra Info, Default Value, Auto-fill in ticket form, Character limit, Placeholder, Has personal info, Allow in my profile and Allow in ticket form, etc.
- Click Submit.
Screenshot 34: Adding New Customer Fields
Editing Customer Fields
- Click on Customer Fields.
- To edit an existing field, click on the Edit button next to the field.
- Make the necessary changes to the field settings.
- Click Submit.
Screenshot 35: Editing Customer Fields
Step 16: Agent Only Fields
- Ticket fields and agent-only fields are essentially identical, with the sole distinction being that the latter is not viewable by customers.
- If agent-only fields are included in the customer ticket list items, customers have the ability to view them in the ticket list.
Adding New Agent-Only Fields
- Click Add New to create a new agent-only field.
- Choose the field type (e.g., text, dropdown, checkbox).
- Configure the field settings (Extra info, Default value, Character limit, Placeholder, Ticket list width, Has personal info etc.)
- Click Submit.
Screenshot 36: Adding New Agent Only Fields
Editing Agent Only Fields
- Go to the SupportCandy plugin menu.
- Click on Agent Only Fields.
- To edit an existing field, click on the Edit button next to the field.
- Make the necessary changes to the field settings.
- Click Submit.
Screenshot 37: Editing Agent Only Fields
Conclusion
In this blog (Part 1 of 3 of the series), we walked you through how to add a helpdesk and ticket system on WordPress using the SupportCandy plugin.
SupportCandy adds to your WordPress site the features of a complete help desk and customer support ticket system. It is one of WordPress's most popular helpdesk and customer support ticketing plugins.
That’s it for this article.
In Part 2 of this series, we will dive deeper into other sections of SupportCandy.
If you need any help related to WordPress, please contact our WordPress experts.
Tutorials
4 min read
How to Create a Staging Site in WordPress using WP Staging plugin
Introduction
When managing a WordPress site, whether it's for blogging, e-commerce, or any professional use, ensuring a smooth, uninterrupted user experience is a must. Here, a staging site turns into a vital resource for WordPress users. By acting as a testing ground, a staging site enables developers and website managers to make and test changes without having an impact on the live website. This is especially crucial when updating WordPress core, themes, or plugins, as these changes may cause incompatibilities or break your website.
In essence, a staging site acts as a critical step in a professional web development workflow, enabling WordPress users to manage and implement website changes systematically and securely.
Why is a staging site important?
Is a staging site really necessary? The importance of a staging site in the context of web development, particularly for WordPress sites, cannot be overstated. A staging site serves several critical roles in ensuring the smooth operation, security, and continuous improvement of a website. Here are the key reasons why a staging site is important:
- Safe Testing Environment:
A staging site provides a safe and isolated platform where all types of changes, updates, and new features can be tested without affecting the live website. This means that any errors, bugs, or issues can be identified and fixed in the staging environment without risking the performance or functionality of the live site.
- Prevents Downtime:
By using a staging site to test changes, you significantly reduce the risk of your live site going down due to a faulty update or incompatible plugin. Downtime can be costly, especially for e-commerce sites or businesses that rely heavily on their online presence.
- Quality Assurance:
Staging sites allow for thorough testing and quality assurance before changes are made live. This includes checking for visual consistency, functionality, compatibility with different browsers and devices, and the overall user experience.
- Update Verification:
WordPress regularly releases updates for its core software. Also, themes and plugins are regularly updated. A staging site enables you to test these updates to ensure they work seamlessly with your site’s customizations and existing setup.
- Secure Development:
Developing directly on a live site can be risky, as it can expose your site to security vulnerabilities. A staging site ensures that development is done in a secure environment, reducing the risk of security breaches.
- Collaboration and Feedback:
For teams, a staging site offers a collaborative environment where developers, designers, content creators, and other stakeholders can work together. It’s easier to gather feedback and make iterative improvements without disrupting the live site.
- Performance Testing:
Staging sites allow you to test the performance impact of your changes. This is particularly important for large-scale sites, where even minor changes can have a significant impact on loading times and overall site performance.
- Backup and Rollback:
In case something goes wrong during the update process, having a staging site means you have a recent backup of your site. This makes it easier to roll back changes if necessary.
Setting Up a Staging Site
Everything is easy in WordPress using plugins, isn’t it? Let’s discover how we can use the WP Staging plugin to set up a new staging site.
Step 1: Search and install the WP Staging plugin
- Search and install the WP Staging plugin on your WP Dashboard. After installation, activate the plugin.
Screenshot 1: Install WP Staging Plugin
- Allow and continue to enable security alerts.
Screenshot 2: Enable security alerts.
Step 2: Create a Staging Site
- Click on Skip and Start WP Staging link. You will be redirected to Staging sites submenu.
Screenshot 3: Skip and Start WP Staging
Screenshot 4: Click on Create Staging Site
- Next, click on “Create Staging Site”. Enter the name of the staging site that you want to create. (This is an optional step).
- Here, the database tables and files are selected by default. However, you can unselect some tables or files if you don't want to clone them.
Screenshot 5: Selecting Database Tables
Screenshot 6: Selecting Files
- Click on “Start Cloning.” A display would show the current status of the staging site's progress.
Screenshot 7: Staging site creation
- When the data is processed, the staging site is ready and the URL is displayed.
Screenshot 9: Staging Site Created Successfully
- If you click on Show Logs, you can see the entire process of logging that was done to create the staging site.
Screenshot 10: Logos
- When you click on the URL of the staging site, you’ll be required to login to the staging site. Use the same credentials as your site.
Screenshot 11: Login Page of Staging Site
- Enter the details, and your staging site is ready to use! You can access your staging site at any time from WP Staging.
Screenshot 12: Access your staging site from WP Staging
Conclusion
In conclusion, setting up a staging site is a crucial step in website development and maintenance.
The WP staging plugin simplifies the process, making it accessible even to those with limited technical knowledge. Remember that a staging site is your best ally in ensuring that your live website runs smoothly, efficiently, and without interruptions.
