NovaShare - WordPress Plugin

A Practical Guide to Setting Up NovaShare on a WordPress Site

NovaShare is best viewed not as a decorative set of icons, but as a working layer between your WordPress content and the external platforms where readers share links. In this guide, we will walk through how to prepare your site, enable buttons in the right places, configure the design, counts, Pinterest settings, editor blocks, Open Graph, UTM tags, link shortening, and troubleshoot common issues.

This article does not repeat the product's short description. What follows is a practical walkthrough: which modes to enable first, where the plugin may be unnecessary, how to avoid duplicate buttons, why counts do not always appear right away, and what to check after each important change.

The main idea is simple: social buttons should help distribute your content without getting in the way of reading, site speed, or analytics. That is why setting up NovaShare should not start with enabling every network at once, but with deciding where users would realistically want to share a page and what result you can actually verify.

When the Plugin Is Truly Useful and When It Is Overkill

NovaShare is a strong fit for sites where content is regularly shared by hand: blogs, media sites, educational projects, recipe sites, product reviews, WooCommerce pages, expert articles, and content with strong visual elements. The plugin adds inline buttons inside content, a floating bar, editor blocks, profile follow buttons, Click to Post, Pinterest image hover pins, highlight and share, UTM tags, Bitly shortening, and metadata settings for social cards.

If your site consists of a handful of static pages and gets little to no social traffic, NovaShare may be more than you need. In that case, standard profile links in the footer or a built-in theme block may be enough. The plugin really shines on sites with frequent publishing, multiple content types, different desktop and mobile use cases, and a need to track which networks actually bring visitors in.

Good Use Cases

For a typical content site, a solid starting setup is inline buttons above or below the article, a floating bar on desktop only, and Click to Post for a few strong quotes. For recipe sites, portfolios, photo-driven reviews, or product pages, it makes sense to spend extra time on Pinterest because image selection and a vertical save-friendly image matter there. For agencies and developers, export and import settings are valuable because they let you reuse the same configuration across client sites.

For a WooCommerce store, NovaShare is useful not as a checkout plugin, but as a tool for spreading product pages and images. It does not need to be enabled on every system page in the store. Buttons make sense on product pages, curated collections, reviews, and content pages, but not on the cart, checkout, account area, or any page where an extra element distracts from completing the action.

When It Is Better to Skip or Delay Installation

Do not install the plugin just because "that is what people do." If the site already runs a heavy page builder, multiple marketing widgets, popups, and ad blocks, first check whether those elements are already creating visual overload. Social buttons will not fix weak content or guarantee traffic. Their job is simply to remove friction for the user who already wants to share the page.

Another reason to wait is incomplete social metadata. If your articles do not have proper images, titles, and descriptions for social networks, the button may open a dull or empty card. In that case, first set up a featured image and configure Open Graph through your SEO plugin or NovaShare's meta box, then enable the buttons on the public-facing site.

Practical check: pick your three most important pages and answer one question: why would a reader share each one? If you only have a clear answer for one page, start with a targeted setup for that content type instead of enabling buttons site-wide.

What to Check Before Installation

NovaShare is a premium plugin, so it is typically installed as a ZIP file through the WordPress admin panel. You do not need a separate WordPress.org login for installation, but you do need working administrator access to the site, a current backup, and a clear idea of which pages will display buttons.

Preparation matters even more if you are replacing an older social sharing plugin. Two sharing systems on the same page almost always lead to extra styles, duplicate buttons, count conflicts, and Open Graph confusion. NovaShare includes a migrator for some popular alternatives, but migration alone does not remove the need to manually verify the result.

Technical Minimum

• Make sure you have WordPress administrator access and the ability to upload ZIP plugins through Plugins and Add New.
• Create a backup of both files and database before importing settings, migrating counts, or replacing an older plugin.
• Write down where social buttons are already being rendered: the theme, page builder, old plugin, widget, shortcode, or custom code.
• Check site caching, CDN, and CSS/JavaScript optimization. After changing button styling, clearing cache is almost always necessary.
• Prepare a list of the social networks that actually matter to your audience instead of turning on every supported option.

Content Preparation

A social button is only useful if the shared link looks good after it is sent. Check that your key pages have a strong title, short description, primary image, and, if Pinterest is part of the strategy, a vertical image version. NovaShare lets you set social images and descriptions at the individual post level, but if you already use Yoast, Rank Math, SEOPress, or another SEO plugin, do not duplicate meta tags unless you have a specific reason.

On older sites, check URL history separately. If the site moved from HTTP to HTTPS, changed domains, updated permalink structure, or renamed important content, social counts may still be tied to older URLs. NovaShare includes recovery settings for cases like this, but they should be enabled deliberately. Otherwise, you may end up looking for the problem in the wrong place.

Installation and the First Check in the Admin Panel

The basic NovaShare installation process is not fundamentally different from installing any other ZIP plugin. In WordPress, open Plugins, then Add New, choose Upload Plugin, upload the archive, and activate the plugin. After activation, the settings are available under Settings - Novashare.

This guide does not cover purchasing, payment, or licensing. The only practical point to understand is that the license is needed for updates and support. After installation, confirm that the plugin opens in the admin panel, shows no critical errors, and is available to users with the administrator role.

A Safe First Launch

1. Open Settings - Novashare and make sure you can see the plugin settings tabs.
2. Do not enable every mode at once. Start with one use case, such as inline buttons for posts.
3. Select 3 to 5 networks that matter to your audience, for example X, Facebook, LinkedIn, Pinterest, Email, or Copy.
4. If you are setting up a blog, enable only the Posts post type. Add pages and custom post types later.
5. Save changes, clear cache, and open a test article in a private browser window.

After the first save, do not evaluate success based only on whether the buttons appear. Check that they are in the right place, do not break spacing, do not cover content on mobile, and open the correct sharing window. If your theme already includes its own share buttons, temporarily disable them or choose a NovaShare mode that does not insert buttons automatically.

Expected result of the first check: only one set of buttons appears on the test post, the selected networks are in the right order, and clicking a button opens a correct share link.

What Not to Do on Day One

Do not enable share counts, UTM tags, Bitly, Pinterest hover pins, highlight and share, and the floating bar all at once. If something looks wrong after that kind of launch, you will not know which feature caused the problem. A much more practical approach is to build the configuration in layers: first placement, then design, then mobile behavior, then counts and analytics.

Do not import settings from another site without reviewing the JSON file and creating a backup first. The official documentation warns that import overwrites current settings. That is convenient for agencies, but on a live site without a backup it can unexpectedly replace colors, post types, and selected networks.

Inline Content and Floating Bar: How to Choose Button Placement

NovaShare has two main display modes: inline buttons inside content and a floating bar. They solve different problems. Inline Content is tied to the act of reading: the buttons appear above the article, below it, or in both places. Floating Bar stays visible during scrolling and works well for long-form content, where a user may decide to share halfway through the article.

A good configuration rarely means "turn both modes on everywhere." For short news posts, a floating bar may be unnecessary. For long guides, it can be useful, but only if it does not overlap a table of contents, an ad block, a sticky header, or mobile navigation. On landing pages, thank-you pages, and utility pages, buttons are usually better disabled per post.

Inline Content for Articles and Pages

In Inline Content, enable Enable Inline Content, choose the post types, and set the Button Position. In most cases, it makes sense to start with a position above content or below content. The "above and below" option can work well for long publications, but on short posts it often feels pushy.

If you are placing buttons with a shortcode or block in a specific location, choose Don't Add to Content. That does not disable the feature. It simply tells the plugin, "do not insert automatically, I will place it myself." This mode is especially useful for GeneratePress Elements, block templates, custom theme areas, and pages where automatic placement lands in the wrong spot.

Practical Position Choices

• Above content - works well for news posts, listicles, and content readers often share before finishing.
• Below content - works well for tutorials, reviews, and guides where the sharing decision comes after the reader gets value.
• Above and below content - works for long-form content, but needs a visual density check.
• Do not add automatically - works best for shortcodes, blocks, theme hooks, and exact placement inside a template.

Floating Bar for Long-Form Content

The floating bar is convenient on desktop, where there is free space along the side. Enable it in Floating Bar, select the post types, and check the container offset. On mobile, the floating bar may become a bottom row, take up too much space, or be hidden depending on your breakpoint settings.

The key setting here is not just visual design, but display logic. NovaShare lets you control whether it appears above or below a breakpoint and whether it displays on the posts page, archives, and home page. At the same time, the official documentation explicitly notes that share counts are not supported on archives. So if you show floating buttons on archive pages, do not expect the count behavior to match what you see on a single post.

How to Check the Floating Bar

1. Open a long article on desktop and scroll to the middle.
2. Check whether the bar covers text, ads, a table of contents, an email signup form, or sticky theme elements.
3. Narrow the browser window to a mobile width and see whether the bar turns into a usable bottom row or disappears.
4. Click several networks and confirm that the URL matches the current post, not an archive page or preview.

If buttons appear twice, the cause is almost always a combination of automatic placement and a manual block or shortcode. The fix is straightforward: keep either automatic output or manual placement, but not both at the same time.

Button Design: Style, Network Order, and Mobile Breakpoints

The visual design of social buttons affects clicks, but it should not compete with the rest of the site's interface. NovaShare gives you settings for size, shape, alignment, spacing, colors, hover states, column layout, and labels. Inline Content supports multiple styles, including solid, inverse, bordered, and minimal variations. Floating Bar offers a simpler set because the bar needs to stay compact.

Start design with network order. Put the 3 or 4 channels your audience actually uses first. For a B2B article, that might be LinkedIn, X, Email, and Copy. For a recipe or visual tutorial, Pinterest, Facebook, Email, and Copy may make more sense. For mobile audiences, WhatsApp, SMS, or Messenger may be useful, but not every mobile-focused network belongs on desktop.

Recommended Starter Set

For most content sites, do not begin with two dozen buttons. The longer the row, the less clear the choice becomes. A practical starting point is 4 to 6 items, including one utility button such as Email, Print, or Copy. Copy is especially useful when readers send links in messengers, work chats, and personal notes.

In NovaShare, networks are selected with a click and reordered by drag and drop. After saving, check the order on the live site, because the real width of the buttons depends on labels, chosen style, and the theme container. If labels are enabled, longer names can wrap or make the row too dense. On mobile, it is often better to hide labels or keep only the most obvious ones.

Buttons That Match the Site Brand

Official social network colors are instantly recognizable, but they do not always fit the design of the site. NovaShare lets you define your own button color, hover color, icon color, and icon hover color. For a more restrained site, it is often better to use a single brand color with a clear hover state. For a blog with strong visual identity, you can keep network colors but reduce size and spacing so the buttons do not look like an ad block.

The Inverse on Hover option adds extra inline JavaScript to pages where the buttons appear. That does not mean you should never use it, but only enable it if the effect is genuinely worth it. If the goal is maximum simplicity and speed, a standard hover color is enough.

Quick Setup for a Typical Blog

• Inline Content: below content, Minimal Label or Solid style, left-aligned or centered depending on the theme.
• Floating Bar: desktop only, 3 to 5 networks, compact shape, no unnecessary labels.
• Mobile: hide the floating bar or keep only a bottom row with the most useful networks.
• Share counts: enable only after confirming they are needed and do not create a visually awkward "zero" effect.

After changing the design, clear the page cache, CDN cache, and CSS optimization cache. NovaShare has had updates where front-facing CSS classes changed, and the developers explicitly recommended clearing cache layers afterward. That is a good general rule: if the buttons still look like the old style, clear cache first instead of rewriting CSS.

Editor Blocks, Shortcodes, and Manual Placement

NovaShare supports the modern block editor: Share Buttons, Follow Buttons, and Click to Post can be inserted directly into content, templates, widgets, or the Customizer. That is an important difference from the older approach, where social buttons were usually rendered only through a global setting or a shortcode.

Manual placement is useful when automatic insertion lands in the wrong spot. For example, the theme may render a featured image, author box, table of contents, and ads before the article, while you want the buttons immediately after the intro paragraph. Or you may want a Follow Buttons block in the sidebar, but share buttons only below the article. In cases like that, blocks and shortcodes give you cleaner control than trying to force one global position to fit everything.

Share Buttons Block

The Share Buttons block can be added from the block inserter or by typing /nova. In the editor sidebar, you can change style, layout, width, alignment, colors, size, shape, labels, breakpoints, counts, and call to action. That makes it useful for individual templates where the buttons should differ from the global configuration.

Here is one practical example: in a blog post template, you can place the block right after the title, choose 4 networks, enable labels, and apply a brand color. At the same time, you can keep the Floating Bar enabled globally for desktop. That way, you avoid duplicating buttons inside content while still giving users two different ways to share.

Follow Buttons Block and Widget

Follow Buttons solve a different problem: not sharing the current page, but sending users to your profiles. The block supports many networks and also lets you add a custom button with an SVG icon. Enter the destination URL or username for each network, then configure shape, size, spacing, labels, open-in-new-tab behavior, and colors.

Do not mix Follow Buttons and Share Buttons in one visual row. Users should immediately understand that one action shares the current content, while the other leads to your profile. Good places for Follow Buttons include the author sidebar, footer, About page, post-subscription area, and contact section.

Shortcodes for Themes, Hooks, and Builders

NovaShare supports the shortcodes [novashare_inline_content], [novashare_floating], and [novashare_follow]. For inline and floating output, do not forget two things: choose the correct post types and set the position to Don't Add to Content if you are placing the buttons manually. Otherwise, you will get duplicates.

In GeneratePress Elements, a block theme, or a page builder, you can output inline buttons via a hook after the title. But if the shortcode is only used for one specific content type, do not enable it globally on every page. One of NovaShare's performance strengths is that styles and scripts should not load where you did not intend to show buttons.

Short Safe HTML Wrapper

If you need to add a little spacing around a shortcode inside a theme hook, use a simple HTML wrapper. This does not modify plugin files and is easy to remove.

<div class="share-after-title" style="margin: 12px 0 18px;">
  [novashare_inline_content]
</div>

After publishing, check the page while logged out of the admin panel. If the buttons do not appear, do not start by blaming the shortcode itself. First check the selected post types and output position in the NovaShare settings.

Counts, Old URL Recovery, and Honest Social Proof

Share counts can strengthen trust in popular content, but they come with limitations. NovaShare supports total share count and network share counts for platforms that still allow those numbers to be queried. The official documentation lists supported sources, but the situation changes over time: X does not provide native counts, LinkedIn discontinued count support, and new Facebook engagement data has been frozen on the platform side. That is why counts should be treated as useful, but never absolute.

The main rule is simple: if the site gets very little sharing, do not show zeros. Set a minimum threshold so counts only appear after they reach a meaningful number. That is more honest and visually cleaner than displaying "0 shares" on every new article.

How to Enable Counts Without Creating Unnecessary Load

In the Inline Content or Floating Bar settings, find the Share Counts section. There, you can enable total share count and network share counts, and choose their position, color, and text case. If you do not need counts, leave them disabled. The official documentation explicitly points out that no related API requests are made unless share counts are enabled.

For X, NovaShare relies on external count services such as TwitCount or OpenShareCount, but those services do not restore a full historical record and may only begin working properly after domain setup. Facebook requires Meta app configuration, but due to the platform's current limitations, new engagement data may not update. So do not promise clients "exact social numbers" as if they were guaranteed metrics.

Recovery After HTTP, Domain, and Permalink Changes

One of NovaShare's stronger features is Social Share Count Recovery. It matters if the site changed protocol, domain, www/non-www format, permalink structure, or the URLs of individual pieces of content. The logic is straightforward: the plugin tries to combine metrics from the old and current URLs so social proof does not disappear after a technical migration.

Before enabling recovery, map the changes. For example: old domain, new domain, old permalink structure, and key renamed posts. Do not enable every option blindly. If the only change was HTTP to HTTPS, you do not also need to specify an old domain. If only one article changed slug, use the previous URL setting on that post instead of turning on a global domain migration.

How to Verify Recovery

1. Open one older high-performing post and manually refresh share counts at the post level if that option is available.
2. Compare the current URL with the historical one: protocol, domain, www, slug, and trailing slash should all match the recovery logic you are using.
3. Wait for the data to refresh, because counts are not fetched instantly across the entire database.
4. If the number still does not appear, check the minimum threshold and the specific network's support, not just the global toggle.

If enabling counts slows the site down, review the refresh rate and the number of networks with active counts. Counts are best used where they truly help: on popular articles, evergreen content, recipes, ranked lists, and pages that already attract social engagement.

Pinterest, Hidden Images, and Managing Share Visuals

NovaShare's Pinterest settings are different from standard social buttons. Here, not only the link and title matter, but also the specific image. The plugin can show image hover pins, control button behavior, change position, shape, and color, add a repin ID, disable pinning on individual images, and use hidden images prepared specifically for Pinterest.

The official documentation separately notes that hover pins are implemented on the public-facing site with inline CSS and no additional JavaScript. For sites built around visual content, that is a meaningful advantage: the button appears when the user interacts with the image, but it does not turn every image into a heavy widget.

Three Button Behavior Modes

The Pinterest settings include several behavior options. Share pin image shares the image the user is interacting with. Share post image emphasizes the featured image of the post. Show image grid lets the user choose from the available pinnable images. For recipes, crafts, galleries, and product roundups, the grid is often more useful because the visitor can pick the strongest visual.

If you use hidden images, prepare a separate vertical visual in the right aspect ratio and upload it in the post meta box or image settings. According to NovaShare's documentation, these hidden images are deferred until user interaction to reduce performance impact. That is not a license to upload oversized files without optimization, but it is a good way to avoid placing a vertical Pinterest banner directly inside the article itself.

Disabling Pinning and Using Image Attributes

Not every image should be saved to Pinterest. Icons, admin panel screenshots, technical diagrams, personal photos, and utility illustrations are often better excluded. In the block editor, NovaShare adds settings for the specific image, so you can disable pinning or specify an alternate image.

The Enable Image Attributes option is useful if you need Pinterest attributes such as data-pin-id, data-pin-media, or data-pin-nopin even when hover pins are not enabled. This is a more advanced setting for sites that carefully manage Pinterest data and browser extensions.

WooCommerce and Pinterest on Product Pages

For WooCommerce, the official documentation provides a dedicated filter that helps add Pinterest image hover pins to the product gallery. Only use it if you clearly understand why pinning belongs on product images, and test it first on a staging copy of the site.

add_filter('woocommerce_single_product_image_thumbnail_html', 'novashare_add_pinterest_images');

The safe place for that code is a snippets plugin or a child theme file. Do not put it in WordPress core, NovaShare's own plugin files, or the parent theme. After adding it, open a product page, hover over a gallery image, and check whether the Pinterest button appears. If the gallery layout breaks or the button appears on the wrong images, disable the snippet and go back to a no-code configuration.

Important nuance: Pinterest logic should be tied to real images users would actually want to save. If the article contains only technical screenshots, hover pins may be unnecessary.

Open Graph, UTM, and Bitly: Connecting Sharing to Analytics

NovaShare does more than render buttons. It can also influence the data social networks read when content is shared. Open Graph meta tags define the title, description, and image used for Facebook, LinkedIn, and similar platforms. UTM parameters help analytics identify which network drove the visit. Bitly shortens long URLs, especially when UTM tags are added.

Open Graph Without Conflict With an SEO Plugin

Open Graph is enabled in NovaShare by default, but the documentation is refreshingly direct: in some cases, it can override existing tags. If your site already uses Yoast, Rank Math, AIOSEO, or SEOPress, decide which tool will be the primary source of social metadata. Two sources can output duplicate tags, and the social network may end up using the wrong one.

A practical approach is this: if your SEO plugin already handles all social cards, leave Open Graph there. Use NovaShare for buttons, Pinterest hidden images, selective block disabling, and local checks. If you do not have an SEO plugin, or it does not cover the use case you need, enable Open Graph in NovaShare and fill in the social media image, title, and description in the post meta box.

UTM Tags for Real Measurement

UTM Tracking is enabled in the Configuration section, inside the Google Analytics block. By default, source can be inserted with {{network}}, medium is usually social, and campaign can be something clear such as novashare or the name of a content campaign. The key is consistency. If you change naming randomly, your reports become harder to read.

Verification is simple: click a share button on a test post and inspect the URL. It should contain utm_source, utm_medium, and utm_campaign. Then open your analytics reports and make sure traffic is grouped the way you intended. If UTM tags make the link too long, connect Bitly.

Bitly and Shortening Limits

NovaShare uses Bitly for short links. In the settings, enable Enable Bitly, add your Generic Access Token, and save changes. The documentation notes that some networks do not allow shortened links, including LinkedIn, Pinterest, and Hacker News. So do not expect a short URL to appear everywhere.

Do not purge short links without a reason. The documentation explains that purging removes stored short links from the database, after which they are generated again during future shares. Free Bitly accounts have monthly shortening limits, so repeated purges can create an unnecessary restriction.

What to Check After Enabling Analytics

• The button opens the URL of the current post, not a preview, archive, or admin page.
• The UTM source matches the selected network, and campaign uses a stable value.
• The Bitly link is generated where the network allows it and does not break the redirect.
• The Open Graph card shows the correct image, title, and description.
• If an SEO plugin is active, the page does not contain duplicate or conflicting Open Graph tags.

The Post Meta Box: Fine-Grained Control Without Global Workarounds

Global settings are convenient as long as the whole site behaves the same way. In practice, there are almost always exceptions: a landing page with no buttons, a review that needs a dedicated Pinterest image, an older article with a previous URL, a post where counts need to be refreshed manually, or a piece where highlight and share distracts from reading. For situations like these, NovaShare adds a post meta box with settings for the current post or page.

This meta box is especially important for editors. A developer may configure the global button output once, but the editorial team still needs control over individual pieces of content: hiding the floating bar on a signup page, adding a vertical Pinterest image to a recipe, defining a social media title for a stronger social headline, or disabling image pins on a technical tutorial full of screenshots.

The Social Card for an Individual Post

In the social media image, title, and description fields, you can define the data used by social networks if NovaShare is responsible for Open Graph. The official documentation provides a recommended format for a standard social card image and a separate format for a Pinterest image. In practice, you should not treat those dimensions as dogma. What matters more is that the image is large, readable, does not crop the main subject, and matches the real content of the page.

If your site already has an SEO plugin, do not use the NovaShare meta box as a second parallel source for the same fields. It is better to choose one tool. Even with an active SEO plugin, the meta box is still useful for more targeted actions: Pinterest hidden images, disabling inline or floating output, refreshing share counts, disabling image pins, and disabling highlight.

Hide Buttons on a Specific Page

One of the most practical use cases is disabling inline buttons or the floating bar on a specific page without breaking the global configuration. For example, you may have buttons enabled on all posts, but also have an editorial page with a lead form where the floating bar hurts focus. There is no need to create a separate post type or edit the theme. Just open the post, find the NovaShare meta box, and enable the hide setting for the mode you do not want.

After saving, check the actual public URL. If you see buttons in preview but not on the published page, the difference may come from the preview URL versus the real permalink. If the opposite happens and the buttons should disappear but remain visible, clear cache and make sure the page does not contain a manual block or shortcode that ignores the global hide toggle.

Refresh Share Counts at the Post Level

When the issue affects one popular piece of content, do not start with purge or global operations. The official documentation recommends refreshing counts at the individual post level first when diagnosing a specific URL. That approach is cleaner: you do not reset the whole site, trigger unnecessary requests, or make troubleshooting harder. You find out faster whether the problem belongs to one page or to the broader configuration.

A typical sequence looks like this: open the post, check the current permalink, make sure share counts are enabled in the relevant mode, review the minimum threshold, then use the post-level refresh option. If the number still does not change, move on to checking network support, the external count service, recovery settings, and whether the URL is accessible to outside services.

Migrating From Another Social Sharing Plugin

If the site is moving from Hubbub/Grow Social, Social Snap, or Social Warfare, review the NovaShare Migrator documentation. The migrator supports transferring share counts, post meta, and Pinterest images for those tools, but that does not mean migration is always necessary. Some data is stored by the social networks themselves and may come back after count configuration. The migrator is most useful when the old plugin stored additional data that would otherwise be lost.

Before migrating, create a backup, disable public output from the old plugin, and make a short list of what must be preserved: counts, social images, Pinterest hidden images, and per-post disables. After migration, check 5 to 10 pieces of content across different scenarios: a new article, an older popular post, a post after a URL change, content with a Pinterest image, and a page where buttons should remain hidden.

Critical post-migration check: the page should not contain two button sources or two Open Graph sources. First get the output clean, then enable counts, UTM tags, and additional visual modes.

Practical Scenario: Configure Sharing for a Blog and Verify the Result

Let us walk through a content-focused WordPress site scenario: you want to add clean buttons to articles, preserve performance, give visitors a quick way to share a quote, and generate measurable traffic in analytics. The goal is not to enable the maximum number of features, but to build a clear configuration you can verify in one pass.

Goal

All blog posts should show inline buttons below the content, desktop should display a compact floating bar, one article should include Click to Post for a quote, and every share link should carry UTM tags. Counts should be enabled only after the basic logic is verified, so visual setup and external API troubleshooting do not get mixed together.

Preparation

• NovaShare is installed and activated.
• Old social buttons from the theme or another plugin are disabled.
• The test post has a featured image, a solid title, and a short description.
• Site cache can be cleared after each important change.

Setup Steps

1. In Inline Content, enable Enable Inline Content, choose Posts, and set the position to Below Content.
2. Enable X, Facebook, LinkedIn, Pinterest, Email, and Copy. Arrange them in the order that matches the site's audience.
3. In Design, choose the style, size, and shape. For the initial setup, keep the size moderate and skip complex hover effects.
4. In Floating Bar, enable the bar for Posts only. On mobile, keep the bottom row only if it does not interfere with the theme interface.
5. In Configuration, enable Enable UTM Tracking. Keep source as {{network}}, medium as social, and campaign as a stable campaign name.
6. In the test article editor, add a Click to Post block after a strong quote. Choose the theme, accent color, and call to action text.
7. Save changes, clear cache, and open the article in a private window.

Verifying the Result

Start by evaluating the visual result before clicking anything: is there one set of inline buttons, is the floating bar visible on desktop, does it avoid covering content, and does Click to Post look correct? Then click Copy and one social network. The link should go to the current post, include UTM tags, and open the expected share window.

After that, check the social card. If the image or description is wrong, identify who controls Open Graph: the SEO plugin or NovaShare. Do not try to fix the problem in two places at once. Choose one source, update the metadata, clear cache, and test again with the social network's debugger if one is available.

A Commonly Missed Detail

If you test buttons in post preview mode, the URL may differ from the public permalink. Counts, UTM tags, and the social card should be checked on the published page or an accessible test URL. On closed staging sites, outside services may not be able to see the page at all, so do not conclude that NovaShare is broken until you confirm the URL is reachable externally.

Performance, Cache, Compatibility, and Safe Improvements

NovaShare is positioned as a lightweight plugin: the official product page highlights a small front-end footprint, no jQuery dependency, inline SVG icons, no third-party icon resources, and custom tables for scalability. Third-party reviews also tend to focus on performance. But even a lightweight plugin can be configured in a heavy-handed way if you enable too many features on every page and ignore caching.

What Affects Performance

First, placement. If buttons are only needed on posts, do not enable them on pages, archives, and the home page. Second, counts. They may require outside APIs and periodic refreshes. Third, visual effects such as inverse on hover, which adds inline JavaScript to pages with buttons. Fourth, Pinterest hidden images: they are deferred until interaction, but the images themselves still need optimization.

If the site uses Perfmatters, WP Rocket, LiteSpeed Cache, Autoptimize, a CDN, or critical CSS, always check the buttons after clearing all relevant cache layers. An older CSS version may show up as "the color did not apply," "the buttons look different," "hover does not work," or "the icons shifted."

Compatibility With Themes and Builders

NovaShare uses a native WordPress-style admin interface and offers several output methods: automatic placement, blocks, shortcodes, a widget, and theme hooks. If the buttons land in the wrong place, that is not always a bug. Often, the theme renders content through a non-standard hook, and the automatic placement ends up before or after an unexpected block.

The fix is to switch to manual placement. Choose Don't Add to Content, insert a block or shortcode in the correct area, and confirm that the post types are still selected. For block themes and the Site Editor, the block is usually the easiest option. For GeneratePress, Kadence hooks, or a custom theme, a shortcode inside a hook element may be more convenient.

Custom CSS Only for NovaShare Elements

NovaShare includes its own Custom CSS field under Configuration. The advantage is that this CSS only loads where the plugin is actually used. Use it for small NovaShare-specific button adjustments, not for general site styling.

Do not paste in CSS that depends on unverified classes from a random forum post. Front-facing classes can change after updates, and old CSS may stop working. If you need a precise adjustment, first inspect the button HTML in your own browser on your own site, then add the smallest possible rule and test again after clearing cache.

Safe Order for Visual Tweaks

1. Start with the built-in settings for color, shape, size, and spacing.
2. If the built-in controls are not enough, add a small CSS rule in NovaShare Custom CSS.
3. Test one post on both desktop and mobile.
4. Clear cache and test again while logged out of the admin panel.
5. If the buttons change after a plugin update, temporarily disable your custom CSS and compare behavior.

If you are a developer, NovaShare includes documented filters and actions such as novashare_network_link, novashare_permalink, novashare_short_link_url, novashare_opengraph_meta_tags, and others. But in a standard setup guide, it is better not to introduce PHP filters just for minor styling tweaks. Code-level filters make sense when you need to change a link, Open Graph output, or integration with custom site logic.

Video: A Quick Visual Walkthrough

If you prefer to see the interface in motion first, you can watch Dave Swift's focused NovaShare video. It gives a good high-level overview of social button setup, the floating bar, Click to Tweet, metadata, and a performance-conscious approach. Use it as a visual companion to this guide, not a replacement for current documentation, because specific interface details and network lists can change over time.

It is especially useful to compare the video with the sections on inline buttons, the floating bar, and Click to Post: first see how the interface logic works, then apply the current settings from the documentation and verify the result on your own site.

Common NovaShare Issues and Troubleshooting

Most NovaShare issues are not caused by installation itself, but by output conditions: selected post types, automatic position, cache, conflicts with an older plugin, expectations around share counts, or social metadata. The best way to troubleshoot is to move from the visible symptom to the relevant setting, rather than changing everything at once.

Buttons Do Not Appear on a Post

Symptom: settings are saved, but no buttons appear on the public post. Possible causes: Enable Inline Content or Floating Bar is not enabled, the required post type is not selected, Don't Add to Content is active, the page is being viewed as an archive, cache is showing an old version, or the post is excluded through the meta box.

What to check: open the settings for the relevant mode, review the post types, then open the editor for the specific post and confirm that the hide toggle is not enabled. After that, clear cache and test the published URL in a private window.

How to fix it: enable the needed mode, select the correct post type, change the position from manual to automatic, or insert the block/shortcode where it belongs. If the buttons only appear after disabling cache, configure exclusions or clear the generated CSS.

Buttons Appear Twice

Symptom: two identical sets of buttons appear above or below the article. In most cases, automatic output is active at the same time as a manual block, shortcode, theme hook, or old social plugin.

What to check: look for a Share Buttons block or the shortcode [novashare_inline_content] inside the content. Then review the Inline Content settings. If a position above or below content is selected there, automatic output is already active.

How to fix it: keep one method only. For manual placement, choose Don't Add to Content. For automatic output, remove the block/shortcode from the post or hook element. Disable older social button plugins completely instead of hiding them with CSS.

Counts Do Not Appear or Look Incomplete

Symptom: the buttons are visible, but the total count or network count does not appear. Causes include counts not being enabled in the relevant mode, a minimum threshold set too high, the network not supporting the current count type, X/Facebook requiring separate setup, or data not yet being fetched after the first visit to the post.

What to check: review Share Counts, the minimum threshold, refresh rate, network support, and published URL availability. For old URLs, check recovery settings. For individual posts, use manual count refresh if it is available in the meta box.

How to fix it: lower the minimum threshold for testing, wait for the next refresh, configure the external count service where needed, or disable counts on newer content. If the platform no longer returns new data, do not try to fix that with CSS or cache changes.

Pinterest Buttons Appear on the Wrong Images

Symptom: the hover pin appears on technical icons, screenshots, or images that should not be saved, or it fails to appear on the image you actually want. Causes may include a broad post type setting, the show-all-pinnable-images mode, missing image attributes, or a specific image without a suitable URL.

What to check: open the Pinterest settings and review button behavior, image grid behavior, and per-image settings in the editor. For a WooCommerce gallery, check whether the official filter is really needed and whether it conflicts with the theme's gallery implementation.

How to fix it: disable pinning on utility images, add a hidden image for the key visual, narrow the selected post types, or change button behavior. If a WooCommerce snippet breaks the gallery, roll the snippet back and test alternatives on a staging site.

The Social Card Shows the Wrong Image

Symptom: sharing opens an old image, an empty card, or a description coming from another plugin. Causes include an Open Graph conflict with an SEO plugin, cached meta tags, a missing social media image, or a social platform still storing an old preview.

What to check: determine who outputs Open Graph: NovaShare or the SEO plugin. Review the page source, then use the debugger for the relevant social platform. If you see duplicate og:image or og:title tags, remove the duplicate source.

How to fix it: keep a single primary Open Graph source, fill in the social image and description, clear site and CDN cache, and refresh the preview with the social platform's tool. Do not toggle every meta setting on and off at once.

The Button Design Changed After an Update

Symptom: buttons shift, colors do not apply, or custom CSS stops working. Possible causes include stale CSS cache, changes to front-facing classes, a conflict with unused CSS optimization, or a custom rule that is too fragile.

What to check: clear WordPress cache, CDN cache, critical CSS, and remove unused CSS output. Temporarily disable custom CSS in NovaShare and compare the baseline output. If the baseline looks fine, the problem is in your customization.

How to fix it: rewrite the CSS against the actual current markup on the site, reduce selector specificity, and avoid depending on outdated classes. In a serious conflict, first return to the default design, then reintroduce your adjustments one at a time.

When NovaShare Is the Right Choice

NovaShare is a strong fit for sites that need social buttons as a clean, fast, measurable layer on top of WordPress content. Its strengths include inline and floating modes, editor blocks, shortcodes, flexible design controls, Pinterest settings, recovery for old URLs, UTM tags, Bitly, and a clear focus on speed.

The best way to roll it out is gradually. Start by enabling one mode for one post type, verify the result, then add mobile logic, Click to Post, Pinterest, or analytics. Turn on counts only where they genuinely add trust and where you understand the platform limitations.

If you need clear WordPress social sharing without unnecessary overhead rather than a huge marketing suite, NovaShare is worth testing. After installation, check the public page, the social card, the UTM link, the mobile view, and the cache behavior. Those checks will tell you whether the site has become easier for readers to use and safer to keep refining.