by
mashdunllc
0 (0 reviews)
SignSealer
Send waivers and agreements from WordPress, and see who has signed. Signing happens on SignSealer; this site keeps ids and status, never evidence.
SignSealer ranks #60,414 among WordPress.org plugins with 0+ active installations, and was last updated Oct 18, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.17.1
Current Version v1.17.1
Updated 1 week ago
Last Update on 18 Oct, 2026
Refreshed 2 days ago
Last Refreshed on
Downloads -80.7% this week
Actively maintained
Rank
#60,414
—
No change
Active Installs
0+
—
No change
KW Avg Position
18.5
0.5 worse
Downloads
124
+1 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
32,846
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 8 more installs to reach 10+
Rank Changes
Current
#60,414
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.17.1
- Last Updated
- Oct 18, 2026
- Requires WP
- 6.4+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- mashdunllc
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about SignSealer
Two reasons. Before SignSealer connects a site it fetches a small page the plugin serves, to check the plugin is really running there and that the request came from this site; it will only do that over https, so nobody can register an application in your site's name. And once connected, SignSealer posts signed statuses back to your site, which must also be over https so those deliveries are private and verifiable.
Yes. This plugin talks to the SignSealer API; it is not a standalone signing tool.
On SignSealer, with its certificate and audit trail. This site keeps the document's id and its status so a page can say whether it is signed.
No, and that is deliberate. See "Three things this plugin refuses to do" above.
Not unless you ask it to. Under SignSealer → Settings → The sign button there is a setting, off by default, that puts a small "Signed with SignSealer" line under the signing button block and the [signsealer_sign] shortcode, linking to signsealer.com. Only a button to your own business's form gets it: nothing else the plugin shows, and not a shortcode pointed at another business. A business with white label is not offered it.
Nothing at SignSealer. Your documents, evidence and certificates are unaffected. Deactivating does not revoke the connection — end that in SignSealer under Developers → Connected apps.
Yes. On a product's edit screen, under General, choose the SignSealer agreement that product needs. When an order containing it is paid — or placed, under WooCommerce → Settings → SignSealer — the document is started for the customer, offered on the thank-you page, in their order email and under My Account, and its status appears on the order screen and in the order notes as SignSealer reports it. Works whether your orders live in posts or in WooCommerce's own order tables.
Yes. Under WooCommerce → Settings → SignSealer choose Before payment. While a customer's cart holds a product whose agreement is unsigned, the cart's checkout button reads Sign the agreement and goes to a page of your site, in your theme, that shows SignSealer's signing page in a frame; a customer who reaches the checkout some other way is sent back to it. The classic checkout and the checkout block both refuse to place the order until SignSealer confirms it is signed, and the order then carries that signed document. SignSealer shows its signing page in a frame only on sites the business has proven, and the site you connected is one. My agreement asks for something the order does not know A template blank that nothing fills — {{location}} on a photo release, say — would make SignSealer refuse to start the document. So on the product's edit screen, under its SignSealer agreement, each such blank has a box: fill it in to answer it for every order of that product, or leave it empty and the customer is asked. Before payment they are asked on the signing page, beside their name and email. After payment the order's Sign link — on the thank-you page, in the order email and under My Account — opens a page of your site that asks, and the agreement is sent once they have answered. The order notes say when an agreement is waiting for that.
Yes. A bookable product is a product, so mark it the same way. A booking you confirm starts its agreement at once, whether or not it has been paid, because the agreement is wanted before the day. The booking's date, time, number of people and resource go to the template as booking_date, booking_time, persons and resource, and the booking's own screen shows where the agreement stands.
Yes, since 1.8.0. Open SignSealer → Bookings, which lists the services in each (in Simply Schedule Appointments, its appointment types), and choose the workflow a booking of each starts. A booking made through the plugin's booking form, or by staff, starts that workflow for the person who booked, and SignSealer emails them the link; LatePoint's confirmation step shows a button to sign too. Since 1.16.0 the person signs on the page in the other two as well. Amelia's booking form opens the agreement over itself when the person presses Book, and makes the booking once it is signed (a booking Amelia takes payment for through Stripe or WooCommerce is made first, and the agreement opens just after). Simply Schedule Appointments opens it over the page as soon as the booking is made, or on the page its form sends people to afterwards. Closed without signing, a button to sign stays on the page, and the email has the link. In Simply Schedule Appointments an appointment waiting on payment starts its agreement once it is booked. The booking fills in booking_date, booking_time, service_name, persons and staff. Any other blank the agreement asks is listed under the service: choose what of the booking answers it (a location blank is given the booking's location, when the plugin has locations set up), or type the answer to use for every booking of that service. A booking saved again — rescheduled, confirmed, paid — starts nothing a second time, and a canceled one starts nothing. If a booking could not start its agreement, SignSealer → Bookings says which and why.